Panic at Inner Ring during new epoch timer processing #205
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#205
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
No panic at new epoch timer tick.
Current Behavior
Steps to Reproduce (for bugs)
It just happened randomly in all Inner Ring nodes in the cluster after some time.
Context
At the same time, neofs-adm couldn't update epoch with
morph force-new-epoch
command, but maybe it is unrelated.Your Environment
Cloud deploy.
Node version:
0948a280