[#1294] docs: Fix description of shard switching mode
All checks were successful
Vulncheck / Vulncheck (push) Successful in 1m3s
Pre-commit hooks / Pre-commit (push) Successful in 1m26s
Build / Build Components (push) Successful in 1m57s
Tests and linters / Run gofumpt (push) Successful in 2m57s
Tests and linters / Tests with -race (push) Successful in 3m16s
Tests and linters / Staticcheck (push) Successful in 3m22s
Tests and linters / Tests (push) Successful in 3m28s
Tests and linters / gopls check (push) Successful in 3m32s
OCI image / Build container images (push) Successful in 4m52s
Tests and linters / Lint (push) Successful in 6m38s

Signed-off-by: Alexander Chuprov <a.chuprov@yadro.com>
This commit is contained in:
Alexander Chuprov 2025-03-04 19:41:53 +03:00 committed by Evgenii Stratonikov
parent 016f2e11e3
commit d951289131

View file

@ -51,10 +51,7 @@ However, all mode changing operations are idempotent.
## Automatic mode changes
Shard can automatically switch to a `degraded-read-only` mode in 3 cases:
1. If the metabase was not available or couldn't be opened/initialized during shard startup.
2. If shard error counter exceeds threshold.
3. If the metabase couldn't be reopened during SIGHUP handling.
A shard can automatically switch to `read-only` mode if its error counter exceeds the threshold.
# Detach shard