[#1294] docs: Fix description of shard switching mode
All checks were successful
DCO action / DCO (pull_request) Successful in 44s
Vulncheck / Vulncheck (pull_request) Successful in 53s
Pre-commit hooks / Pre-commit (pull_request) Successful in 1m29s
Build / Build Components (pull_request) Successful in 1m34s
Tests and linters / Run gofumpt (pull_request) Successful in 2m0s
Tests and linters / Tests (pull_request) Successful in 2m8s
Tests and linters / Staticcheck (pull_request) Successful in 2m9s
Tests and linters / gopls check (pull_request) Successful in 3m1s
Tests and linters / Lint (pull_request) Successful in 3m11s
Tests and linters / Tests with -race (pull_request) Successful in 3m52s

Signed-off-by: Alexander Chuprov <a.chuprov@yadro.com>
This commit is contained in:
Alexander Chuprov 2025-02-12 19:38:55 +03:00
parent fe0cf86dc6
commit 8f070d8095
Signed by: achuprov
GPG key ID: 2D916FFD803B0EDD

View file

@ -51,11 +51,13 @@ 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: 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. 1. If the metabase was not available or couldn't be opened/initialized during shard startup.
2. If shard error counter exceeds threshold. 2. If shard error counter exceeds threshold.
3. If the metabase couldn't be reopened during SIGHUP handling. 3. If the metabase couldn't be reopened during SIGHUP handling.
If switching to `read-only` is impossible, the shard will switch to `degraded-read-only`.
# Detach shard # Detach shard
To detach a shard use `frostfs-cli control shards detach` command. This command removes the shards from the storage To detach a shard use `frostfs-cli control shards detach` command. This command removes the shards from the storage