Metabase keep opened after shard moved to degraded-read-only mode trough config #959
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#959
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?
Expected Behavior
Metabase should be closed after shard moved to degraded-read-only mode trough config in the same way as moved trough control command.
Current Behavior
Metabase keep opened after shard moved to degraded-read-only mode trough config.
Metabase closed after shard moved to degraded-read-only mode trough config control command.
Steps to Reproduce (for bugs)
Regression
No
Version
Your Environment
Cloud
4 nodes
Panic after the following steps:
Need to initialize
fstree
inDEGRADED
mode too:Was #987 tested at all, or why didn't we catch it?
Was not tested under pressure - that is the reason. When the virtual cluster was checked, there were no errors in the log, that is why the fix was partial.