-
Notifications
You must be signed in to change notification settings - Fork 6
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
Restart with ctrl-c during replay of forkdb spams log #869
Comments
It is easy to reproduce manually. Sync to EOS mainnet with a large sync span of say 3000. Shut down while syncing. Note a large number of blocks written to forkdb. If not repeat until you get a large number in the forkdb. Restart the node. Ctrl-c while it is replaying the forkdb. |
We just need to check for app is_quitting in the loop that applies blocks from the forkdb. Where this log statement is at. |
It is stuck in the loop because we do check in the maybe switch forks which exits that, but then we call it again over and over. |
Yes, the fix is obvious. I'll just go with it I guess. |
It does finish but this should be interrupted so it exits right away instead of replaying all the blocks in the forkdb.
The text was updated successfully, but these errors were encountered: