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

Syncing Node 8 Months Behind – Seeking Faster Sync Options #166

Open
Parmanand0712 opened this issue Oct 18, 2024 · 1 comment
Open

Syncing Node 8 Months Behind – Seeking Faster Sync Options #166

Parmanand0712 opened this issue Oct 18, 2024 · 1 comment

Comments

@Parmanand0712
Copy link

Parmanand0712 commented Oct 18, 2024

I have started optimism full node with Docker by following the documentation and changed the db.engine from Pebble to LevelDB in the scripts/start-op-geth.sh file because I was getting an error. Now the node has started syncing, and the logs show it is syncing blocks that are 8 months and 4 days old.

op-geth-1 | INFO [10-18|07:55:49.954] Starting work on payload id=0x02f90360aa5113d5
op-geth-1 | INFO [10-18|07:55:50.073] Imported new potential chain segment number=116,248,797 hash=496ecb..a7b48a blocks=1 txs=24 mgas=10.926 elapsed=109.590ms mgasps=99.697 age=8mo4d16h snapdiffs=5.36MiB triedirty=1023.42MiB
op-geth-1 | INFO [10-18|07:55:50.077] Chain head was updated number=116,248,797 hash=496ecb..a7b48a root=67ff14..04c677 elapsed=2.834151ms age=8mo4d16h
op-geth-1 | INFO [10-18|07:55:50.180] Starting work on payload id=0x02515e308442f692
op-geth-1 | INFO [10-18|07:55:50.273] Imported new potential chain segment number=116,248,798 hash=7d6c9b..c952b2 blocks=1 txs=24 mgas=6.605 elapsed=82.827ms mgasps=79.739 age=8mo4d16h snapdiffs=5.37MiB triedirty=1023.67MiB
op-geth-1 | INFO [10-18|07:55:50.276] Chain head was updated number=116,248,798 hash=7d6c9b..c952b2 root=a4e4d2..3c4e0d elapsed=2.182358ms age=8mo4d16h

Is it okay to wait, and will it sync with the latest block soon, or do I need to take any steps to speed up the sync?

@Chomtana
Copy link
Collaborator

It's possibly that snap sync is not supported by a LevelDB

You can try to find an OP mainnet LevelDB snapshot provider and extract them to the op-geth datadir in the docker volume.

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

2 participants