diff options
author | Marcel Amirault <mamirault@gitlab.com> | 2019-07-01 03:36:23 +0000 |
---|---|---|
committer | Evan Read <eread@gitlab.com> | 2019-07-01 03:36:23 +0000 |
commit | 20654fb9bf7673cf4f925f36e7bdc4818233cbb9 (patch) | |
tree | 46af5c176d6aedcb42ba9a9d47683c52af813cb4 /doc/administration/database_load_balancing.md | |
parent | 276038c2f7c7c441d5b0f097077175b8ea8f8a16 (diff) | |
download | gitlab-ce-20654fb9bf7673cf4f925f36e7bdc4818233cbb9.tar.gz |
Enforce consistent prefix for bullet lists
Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
Diffstat (limited to 'doc/administration/database_load_balancing.md')
-rw-r--r-- | doc/administration/database_load_balancing.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/administration/database_load_balancing.md b/doc/administration/database_load_balancing.md index 7f3be402b84..98404ff2a10 100644 --- a/doc/administration/database_load_balancing.md +++ b/doc/administration/database_load_balancing.md @@ -40,16 +40,16 @@ For example, say you have a primary (`db1.gitlab.com`) and two secondaries, `db2.gitlab.com` and `db3.gitlab.com`. For this setup you will need to have 3 load balancers, one for every host. For example: -* `primary.gitlab.com` forwards to `db1.gitlab.com` -* `secondary1.gitlab.com` forwards to `db2.gitlab.com` -* `secondary2.gitlab.com` forwards to `db3.gitlab.com` +- `primary.gitlab.com` forwards to `db1.gitlab.com` +- `secondary1.gitlab.com` forwards to `db2.gitlab.com` +- `secondary2.gitlab.com` forwards to `db3.gitlab.com` Now let's say that a failover happens and db2 becomes the new primary. This means forwarding should now happen as follows: -* `primary.gitlab.com` forwards to `db2.gitlab.com` -* `secondary1.gitlab.com` forwards to `db1.gitlab.com` -* `secondary2.gitlab.com` forwards to `db3.gitlab.com` +- `primary.gitlab.com` forwards to `db2.gitlab.com` +- `secondary1.gitlab.com` forwards to `db1.gitlab.com` +- `secondary2.gitlab.com` forwards to `db3.gitlab.com` GitLab does not take care of this for you, so you will need to do so yourself. @@ -209,9 +209,9 @@ without it immediately leading to errors being presented to the users. The load balancer logs various messages, such as: -* When a host is marked as offline -* When a host comes back online -* When all secondaries are offline +- When a host is marked as offline +- When a host comes back online +- When all secondaries are offline Each log message contains the tag `[DB-LB]` to make searching/filtering of such log entries easier. For example: |