Move shard to read-only if there were problems with blobstor #446
Labels
No Label
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 Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#446
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Currently we move to a DEGRADED-READ-ONLY if error counter exceeds the threshold
fb8fee0c8e/pkg/local_object_storage/engine/engine.go (L90)
If there we problems with the blobstor, degraded mode is an overkill, we should just move to read-only.
Possible approach:
metaerr
wrapper similar to how we handle logical errors.metabase
,pilorama
andwritecache
packages.This way we should make less errors in error handling.
Consider having 2 errors counters with the same threshold (we can report cumulative counter in control service for now).