[#1294] docs: Fix description of shard switching mode #1645
No reviewers
dstepanov-yadro
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1645
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "achuprov/frostfs-node:bugfix/fix_shard_docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Close #1294
Signed-off-by: Alexander Chuprov a.chuprov@yadro.com
@ -56,3 +56,4 @@2. If shard error counter exceeds threshold.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`.It is not true, see
func (e *StorageEngine) moveToDegraded(ctx context.Context, sh *shard.Shard, errCount uint32, isMeta bool) {8f070d8095to4c6a3ba0fcNew commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
@ -53,3 +53,3 @@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.That's not true for 1.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.