diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-29 18:09:48 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-29 18:09:48 +0300 |
| commit | f4d51a9f71cf3d4b0874a3e1948fe3c1ea193c4d (patch) | |
| tree | 7ae3da76e824c435167dd108721c0124ad2ee484 /doc/development/geo.md | |
| parent | 2dedd78ef505a0ab0a379c7340a3fcba56ada663 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/geo.md')
| -rw-r--r-- | doc/development/geo.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/geo.md b/doc/development/geo.md index 38245e5f4e5..91e3722d1d6 100644 --- a/doc/development/geo.md +++ b/doc/development/geo.md @@ -368,12 +368,12 @@ All Geo **secondary** nodes are read-only. The general principle of a [read-only database](verifying_database_capabilities.md#read-only-database) applies to all Geo **secondary** nodes. So the -`Gitlab::Database.read_only?` method will always return `true` on a +`Gitlab::Database.main.read_only?` method will always return `true` on a **secondary** node. When some write actions are not allowed because the node is a -**secondary**, consider adding the `Gitlab::Database.read_only?` or -`Gitlab::Database.read_write?` guard, instead of `Gitlab::Geo.secondary?`. +**secondary**, consider adding the `Gitlab::Database.main.read_only?` or +`Gitlab::Database.main.read_write?` guard, instead of `Gitlab::Geo.secondary?`. The database itself will already be read-only in a replicated setup, so we don't need to take any extra step for that. |