Updated on April 8, 2022
Migrate the database
As of v21.5.0, new Teku installations use a LevelDB2 database. Previous Teku versions use RocksDB which continues to be supported.
LevelDB2 databases use less memory and proves to be more stable with Teku.
Teku nodes running in archive mode must resynchronize from genesis to migrate from RocksDB to LevelDB2. Use the
migrate-database subcommand to migrate the database.
Once migration completes there will be two databases in Teku’s data folder. Manually verify that Teku starts
and has the expected data before you remove the RocksDB database.
You need double the disk space of the existing Teku storage folder for the migration process. Once you are satisfied with the migration then you can delete the RocksDB to free up space.
Ensure that Teku isn’t running when using the
subcommand. The duration of the migration depends on various factors, but principally on the disk speed. Status updates
display during the migration process. To migrate the database:
Shut down the local Teku instance.
teku migrate-database --data-path /etc/teku/data/
If not supplied
The migration process informs you if it succeeded, or provides context to errors. If successful, then confirm Teku functions correctly.
teku --data-path /etc/teku/data/
If Teku is running correctly, remove the
beacon.olddirectory from the
If migration fails, resolve any issues and retry. Contact support on the Teku Discord channel if you need help resolving issues.
Users can manually migrate Teku nodes running a RocksDB database to a LevelDB2 database if the Teku node runs in prune mode.
To migrate a RocksDB database in prune mode to a LevelDB2 database:
Download the latest finalized state from a beacon node:
curl -o state.ssz -H 'Accept: application/octet-stream' http://other-node:5051/eth/v2/debug/beacon/states/finalized
This step is optional, you can also supply the finalized checkpoint state via URL from a beacon chain node or Infura when restarting Teku in the step below.
Stop the Teku node you intend to migrate.
beacondirectory in your data path.
Ensure not to delete the
validatordirectory if one is present as this contains your slashing protection data.
Restart Teku and specify the downloaded finalized state using the
Teku creates a LevelDB2 database, and starts from the specified recent state. Teku should be in sync and validating within minutes.