-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
Ancient storage on archive nodes #20647
Comments
It should be of the same size on both full node and archive node. The ancient folder however only stashes away past blocks and receipts. Since the crux of the archive node database is state, that will still linger in leveldb. |
Hi @karalabe, our archive disk space never grows past a certain point and our logs show this crucial information every 1 minute.
I believe this is where the 'freezer' populates the ancient data folder from chaindata folder and ours seem to be stuck at block 5546811. I understand that debug.setHead("0x593710") resets the chain to 5546800 but redownloading the remainder of the chain will take time for an archive node. Is there any other ways to repair this specific block without rewinding the headchain? System information Geth version: 1.9.14 |
Any updates on this issue @karalabe? |
The underlying issue was fixed, though AFAIK it should only ever happen on Clique networks (i.e. Rinkeby). I'm unsure how to fix it though without a resync unfortunately. |
We're experiencing this issue on mainnet :( |
Problem
Ancient storage is a great feature which works well for full mainnet nodes in particular:
However, it's not remotely as good for archive mainnet node (where it will be the most valuable):
Both nodes are completely synced and have been running for a while.
Is there a way to improve it?
System information
Geth version:
1.9.10
OS & Version: Linux
The text was updated successfully, but these errors were encountered: