Skip to content
Snippets Groups Projects
Commit 47132616 authored by Marcel Amirault's avatar Marcel Amirault :interrobang:
Browse files

Merge branch 'praefect-configuration-tweaks' into 'master' 

Gitaly Cluster configuration tweaks

See merge request !71348
parents a61764ba 87299e14
No related branches found
No related tags found
1 merge request!71348Gitaly Cluster configuration tweaks
Pipeline #379949012 failed
Stage: sync
Stage: prepare
Stage: build-images
Stage: fixtures
Stage: test
Stage: post-test
Stage: review-prepare
Stage: review
Stage: qa
Stage: post-qa
Stage: pages
Pipeline: CNG-mirror

#379954583

    Hide whitespace changes
    Inline Side-by-side
    doc/administration/gitaly/praefect.md
    + 1
    − 6
    View file @ 47132616
    ......@@ -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).
    > - 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
    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
    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.
    ......
    0% or .
    You are about to add 0 people to the discussion. Proceed with caution.
    Finish editing this message first!
    Please register or to comment