[#1294] docs: Fix description of shard switching mode
All checks were successful
DCO action / DCO (pull_request) Successful in 41s
Vulncheck / Vulncheck (pull_request) Successful in 54s
Build / Build Components (pull_request) Successful in 1m27s
Pre-commit hooks / Pre-commit (pull_request) Successful in 1m28s
Tests and linters / Run gofumpt (pull_request) Successful in 1m35s
Tests and linters / Staticcheck (pull_request) Successful in 1m57s
Tests and linters / Tests with -race (pull_request) Successful in 2m33s
Tests and linters / Lint (pull_request) Successful in 2m41s
Tests and linters / Tests (pull_request) Successful in 2m57s
Tests and linters / gopls check (pull_request) Successful in 3m16s

Signed-off-by: Alexander Chuprov <a.chuprov@yadro.com>
This commit is contained in:
Alexander Chuprov 2025-02-17 12:41:45 +03:00
parent fe0cf86dc6
commit 4c6a3ba0fc
Signed by: achuprov
GPG key ID: 2D916FFD803B0EDD

View file

@ -51,7 +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:
Shard can automatically switch to a `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.