-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Blockchain size after launch node from snapshot #171
Comments
seam to me , erery day 50~80GB |
we are seeing the same with 1.0.7 ... |
Same size increase for us, hope geth snapshot will be backported to BSC node so we will get offline DB pruning and snapshot sync. |
The issue is fixed #190, you can compile it from master branch. |
@guagualvcha will the node version update fix the problem on an existing node or does it require fresh sync? |
@APshenkin try this method #189 (comment) Also there is a new bsc based on |
The issue is fixed #190, closing |
* Enable Canyon via the superchain registry * Rename PostCanyon to Canyon
System information
Geth version:
geth version
1.0.7OS & Version: Docker
Commit hash : (if
develop
)After downloading snapshot
and running the node we were able to sync it, but size of node was increased dramatically
We are running node in
--syncmode full
but not archive (--gcmode=full
).Previously we had BSC node that was synced from scratch (without snapshot) and its size was ~ 500 GB. But this node got corrupt the state (hello from #159). So we started syncing from snapshot
So my question is why when starting node from snapshot that Binance provide node size increases two times?
The text was updated successfully, but these errors were encountered: