Pruning the execution client to free up disk space
Execution clients (formerly known as eth1 nodes) grow quickly. Run this process to prune the blockchain and free up space.
Quick steps guide
The following steps align with our mainnet guide. You may need to adjust file names and directory locations where appropriate. The core concepts remain the same.
🗡️ Why do I want to prune my execution client?
Free up gigs of precious disk space. Typically 200gb or more is common.
🤖 Pre-requisites
Works with geth currently. Erigon and Besu prune automatically.
Ensure at least 50+ GB of free disk space is available otherwise database corruption may occur.
🚧 How to prune execution client
Ensure adequate failover or backup execution clients are configured for use with your beacon-chain node before proceeding. geth is offline and unavailable during this process.
1. Note how much disk space is currently used and stop the execution client
2. Start the pruning process and monitor it's process.
🔥 Geth pruning Caveats:
Pruning can take a few hours or longer (typically 2 to 10 hours is common) depending on your node's disk performance.
There are three stages to pruning: iterating state snapshot, pruning state data and compacting database.
"Compacting database" will stop updating status and appear hung. Do not interrupt or restart this process. Typically after an hour, pruning status messages will reappear.
3. Once the pruning is finished, restart the execution client service.
4. Compare the disk space of the node after pruning.
Nice work. Enjoy the extra disk breathing room.
🤖 Start staking by building a validator
Visit here for our Mainnet guide
Congrats on completing the guide. ✨
Did you find our guide useful? Send us a signal with a tip and we'll keep updating it.
It really energizes us to keep creating the best crypto guides.
Use cointr.ee to find our donation addresses. 🙏
Any feedback and all pull requests much appreciated. 🌛
Last updated