Blockchain size after launch node from snapshot

[APshenkin]

System information

Geth version: geth version 1.0.7
OS & Version: Docker
Commit hash : (if develop)

After downloading snapshot

https://s3.ap-northeast-1.amazonaws.com/dex-bin.bnbstatic.com/s3-witness-data-download/chaindata-2021-04-15.zip?AWSAccessKeyId=AKIAYINE6SBQPUZDDRRO&Expires=1644459350&Signature=a4vfmga8%2BRwNZl3boisIMEdSWbA%3D

and running the node we were able to sync it, but size of node was increased dramatically

1013G	./bsc-node

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?

[a04512]

seam to me ， erery day 50~80GB

[mtbitcoin]

we are seeing the same with 1.0.7 ...

[Zorato]

Same size increase for us, hope geth snapshot will be backported to BSC node so we will get offline DB pruning and snapshot sync.

[unclezoro]

The issue is fixed #190, you can compile it from master branch.

[easeev]

@guagualvcha will the node version update fix the problem on an existing node or does it require fresh sync?

[gituser]

@APshenkin try this method #189 (comment)

Also there is a new bsc based on geth v1.10 in https://github.com/binance-chain/bsc/commits/upgrade_1.10.2

[unclezoro]

The issue is fixed #190, closing