-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
network is hangout at Ancient blocks frozen already
#20286
Comments
Actually it's the expected behavior. You can see it's a debug level log. So the mechanism of freezer is: whenever there are some blocks stable enough, freezer will move these blocks from "Live database" (leveldb) into "Ancient database"(flatten file). So that freezer will have an endless loop to check the stable block every minute. If However there is a special case => Fast Sync In the fast sync, we will write "stable" chain data into "Ancient database" directly. Basically all blocks below the checkpoint are regarded as stable. So it can happen that after syncing, the block with number |
Thank @rjl493456442 for your detail explanation. By the way, still don't understand why the all the validators with fast-sync stop working after freezing. I need to investigate more. |
Can this issue be closed then? |
@hadv No idea. But I think it's not relevant to this issue. So I will just close it and you can open another one with some logs we can investigate |
chain is stop working when freezer happen
System information
Geth version:
1.9.6 stable
OS & Version: Linux
Commit hash : (if
develop
)Expected behaviour
chain should continue working even freezer happen
Actual behaviour
chain is stop working at a specific blocknumber
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: