-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epoch hangs at one node #2212
Comments
This could be related to unable to force-new-epoch |
Right before the 180 epoch tick:
|
Closed via #2220. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have faced problem when one of the node left at 179 epoch while other nodes were at 189:
Please find output from the
netmap snapshot
command:Also tried to issue 'force-new-epoch' command, please find result below:
Expected Behavior
All nodes have to be at the same epoch.
Possible Solution
Restart 3 services helped me to reach consistency between nodes epoch:
Steps to Reproduce (for bugs)
Nodes had been used for failover tests during 3 days where tests are aimed to kill each service and several "healthcheck" commands were issued against service to 100% sure that service has been restarted and ready to process.
Logs.zip
Your Environment
NeoFS Inner Ring node
Version: v0.35.0-11-g1a7c827a-dirty
GoVersion: go1.18.4
NeoFS Storage node
Version: v0.35.0-11-g1a7c827a-dirty
GoVersion: go1.18.4
NeoGo
Version: 0.100.1-pre-1-g0cb86f39
GoVersion: go1.18.4
The text was updated successfully, but these errors were encountered: