diff options
| author | Shan <s.gohar@gmail.com> | 2019-08-29 21:48:55 +0000 |
|---|---|---|
| committer | Shan <s.gohar@gmail.com> | 2019-08-29 21:48:55 +0000 |
| commit | be685251b0786e1577d9bfc591c36ef0f13c2425 (patch) | |
| tree | cc2ba37e74c95b15503c4bd7c961b4ac418b1db8 | |
| parent | 873a344e8605310254d8441ac2c77d730c391aea (diff) | |
| download | gitlab-ce-be685251b0786e1577d9bfc591c36ef0f13c2425.tar.gz | |
Fixed spelling
| -rw-r--r-- | doc/development/git_object_deduplication.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/git_object_deduplication.md b/doc/development/git_object_deduplication.md index 4dd1edf9b5a..e8af6346524 100644 --- a/doc/development/git_object_deduplication.md +++ b/doc/development/git_object_deduplication.md @@ -186,7 +186,7 @@ When a pool repository record is created in SQL on a Geo primary, this will eventually trigger an event on the Geo secondary. The Geo secondary will then create the pool repository in Gitaly. This leads to an "eventually consistent" situation because as each pool participant gets -synchronized, Geo will eventuall trigger garbage collection in Gitaly on +synchronized, Geo will eventually trigger garbage collection in Gitaly on the secondary, at which stage Git objects will get deduplicated. > TODO How do we handle the edge case where at the time the Geo |