History

Pirate Praveen b03c211899 New upstream version 9.2.10+dfsg		2017-08-17 22:00:37 +05:30
..
database.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30
gitlab.md	New upstream version 8.13.3+dfsg1	2016-11-03 12:29:30 +05:30
load_balancer.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30
nfs.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30
README.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30
redis.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30
redis_source.md	New upstream version 9.2.10+dfsg	2017-08-17 22:00:37 +05:30

README.md

High Availability

GitLab supports several different types of clustering and high-availability. The solution you choose will be based on the level of scalability and availability you require. The easiest solutions are scalable, but not necessarily highly available.

Architecture

There are two kinds of setups:

active/active
active/passive

Active/Active

This architecture scales easily because all application servers handle user requests simultaneously. The database, Redis, and GitLab application are all deployed on separate servers. The configuration is only highly-available if the database, Redis and storage are also configured as such.

Follow the steps below to configure an active/active setup:

Active/Passive

For pure high-availability/failover with no scaling you can use an active/passive configuration. This utilizes DRBD (Distributed Replicated Block Device) to keep all data in sync. DRBD requires a low latency link to remain in sync. It is not advisable to attempt to run DRBD between data centers or in different cloud availability zones.

Components/Servers Required: 2 servers/virtual machines (one active/one passive)