TrueCloudLab/frostfs-node
20
1
Fork 28
Code Issues 106 Pull requests 4 Projects Releases 2 Activity Actions

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

Browse source 
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
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/shard-modes.md
View file

@ -51,7 +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: 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.