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

Ancient storage on archive nodes #20647

Closed
easeev opened this issue Feb 11, 2020 · 5 comments
Closed

Ancient storage on archive nodes #20647

easeev opened this issue Feb 11, 2020 · 5 comments

Comments

@easeev
Copy link

easeev commented Feb 11, 2020

Problem

Ancient storage is a great feature which works well for full mainnet nodes in particular:

/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/sdb                491.2G    337.6G    153.5G  69% /root
/dev/sdc                491.2G    143.9G    347.2G  29% /ancient

However, it's not remotely as good for archive mainnet node (where it will be the most valuable):

~/.ethereum/geth/chaindata # du -h
36.7G   ./ancient
3.5T    .

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

@karalabe
Copy link
Member

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.

@kutysam
Copy link

kutysam commented May 19, 2020

Hi @karalabe, our archive disk space never grows past a certain point and our logs show this crucial information every 1 minute.

ERROR[05-19|03:15:57.287] Block receipts missing, can't freeze number=5546811 hash="12262e…08051e"

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
OS & Version: Linux

@easeev
Copy link
Author

easeev commented Jun 11, 2020

Any updates on this issue @karalabe?

@karalabe
Copy link
Member

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.

@easeev
Copy link
Author

easeev commented Jun 11, 2020

The underlying issue was fixed, though AFAIK it should only ever happen on Clique networks (i.e. Rinkeby).

We're experiencing this issue on mainnet :(

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

3 participants