Skip to content
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

Forcefully killing and restarting a node results in failure to synchronize blocks #2783

Closed
MockY-B opened this issue Dec 3, 2024 · 1 comment
Assignees

Comments

@MockY-B
Copy link

MockY-B commented Dec 3, 2024

System information

Geth version: 1.4.16-e2f2111a-20241129
OS & Version: Linux
Commit hash: e2f2111

Expected behaviour

Forcefully killing(kill -9) and restarting a node should allow it to quickly synchronize blocks.

Actual behaviour

The node is unable to synchronize blocks after being forcefully killed and restarted.

Steps to reproduce the behaviour

  1. Continuously send transactions to the node until its memory usage reaches approximately 45GB.
  2. Forcefully kill and restart the node.

Backtrace

@MockY-B
Copy link
Author

MockY-B commented Dec 31, 2024

verify pass

@MockY-B MockY-B closed this as completed Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants