Compare commits

...
Sign in to create a new pull request.

1 commit

Author SHA1 Message Date
ae64e09ead
[#1294] docs: Fix description of shard switching mode
All checks were successful
DCO action / DCO (pull_request) Successful in 43s
Vulncheck / Vulncheck (pull_request) Successful in 1m35s
Pre-commit hooks / Pre-commit (pull_request) Successful in 1m52s
Build / Build Components (pull_request) Successful in 1m57s
Tests and linters / Run gofumpt (pull_request) Successful in 3m11s
Tests and linters / Lint (pull_request) Successful in 3m24s
Tests and linters / Staticcheck (pull_request) Successful in 3m39s
Tests and linters / Tests with -race (pull_request) Successful in 3m54s
Tests and linters / Tests (pull_request) Successful in 4m4s
Tests and linters / gopls check (pull_request) Successful in 4m23s
Signed-off-by: Alexander Chuprov <a.chuprov@yadro.com>
2025-03-04 19:43:10 +03:00

View file

@ -51,10 +51,7 @@ However, all mode changing operations are idempotent.
## Automatic mode changes ## Automatic mode changes
Shard can automatically switch to a `degraded-read-only` mode in 3 cases: A shard can automatically switch to `read-only` mode if its error counter exceeds the threshold.
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.
# Detach shard # Detach shard