[#1294] docs: Fix description of shard switching mode
All checks were successful
DCO action / DCO (pull_request) Successful in 34s
Tests and linters / Run gofumpt (pull_request) Successful in 49s
Vulncheck / Vulncheck (pull_request) Successful in 1m29s
Pre-commit hooks / Pre-commit (pull_request) Successful in 1m58s
Build / Build Components (pull_request) Successful in 2m5s
Tests and linters / Staticcheck (pull_request) Successful in 2m48s
Tests and linters / gopls check (pull_request) Successful in 3m17s
Tests and linters / Tests (pull_request) Successful in 2m49s
Tests and linters / Tests with -race (pull_request) Successful in 3m27s
Tests and linters / Lint (pull_request) Successful in 3m35s

Signed-off-by: Alexander Chuprov <a.chuprov@yadro.com>
This commit is contained in:
Alexander Chuprov 2025-03-04 19:41:53 +03:00
parent fe0cf86dc6
commit 5a25fb4594
Signed by: achuprov
GPG key ID: 2D916FFD803B0EDD

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