Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
87299e14
Commit
87299e14
authored
Sep 30, 2021
by
Christiaan Conover
Committed by
Marcel Amirault
Sep 30, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Gitaly Cluster configuration tweaks
parent
aff5848f
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
6 deletions
+1
-6
doc/administration/gitaly/praefect.md
doc/administration/gitaly/praefect.md
+1
-6
No files found.
doc/administration/gitaly/praefect.md
View file @
87299e14
...
@@ -1309,12 +1309,7 @@ To minimize data loss in GitLab 13.0 to 14.0, Gitaly Cluster:
...
@@ -1309,12 +1309,7 @@ To minimize data loss in GitLab 13.0 to 14.0, Gitaly Cluster:
new primary. If the failed primary contained unreplicated writes,
[
data loss can occur
](
#check-for-data-loss
)
.
new primary. If the failed primary contained unreplicated writes,
[
data loss can occur
](
#check-for-data-loss
)
.
> - Removed in GitLab 14.1. Instead, repositories [become unavailable](#unavailable-repositories).
> - Removed in GitLab 14.1. Instead, repositories [become unavailable](#unavailable-repositories).
In GitLab 13.0 to 14.0, when Gitaly Cluster switches to a new primary, repositories enter
When Gitaly Cluster switches to a new primary in GitLab 13.0 to 14.0, repositories enter
read-only mode if they are out of date. This can happen after failing over to an outdated
secondary. Read-only mode eases data recovery efforts by preventing writes that may conflict
with the unreplicated writes on other nodes.
When Gitaly Cluster switches to a new primary In GitLab 13.0 to 14.0, repositories enter
read-only mode if they are out of date. This can happen after failing over to an outdated
read-only mode if they are out of date. This can happen after failing over to an outdated
secondary. Read-only mode eases data recovery efforts by preventing writes that may conflict
secondary. Read-only mode eases data recovery efforts by preventing writes that may conflict
with the unreplicated writes on other nodes.
with the unreplicated writes on other nodes.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment