Clarify scenario with change shard mode to DEGRADED_READ_ONLY #1294
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 project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1294
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Now documentation contains phrase
Shard can automatically switch to a degraded-read-only: If shard error counter exceeds threshold.
However, this is not the case now.
Now
Shard can automatically switch to a read-only: If shard error counter exceeds threshold.
Need to clarify scenario with change shard mode to DEGRADED_READ_ONLY.to Need to clarify scenario with change shard mode to DEGRADED_READ_ONLYNeed to clarify scenario with change shard mode to DEGRADED_READ_ONLYto Clarify scenario with change shard mode to DEGRADED_READ_ONLY