migrate-database
Migrate the database to a LevelDB2 database.
As of v21.5.0, new Teku installations use a LevelDB2 database. Previous Teku versions use RocksDB which continue to be supported.
Before running the database migration, you must shut down the local Teku instance and confirm the process has fully exited and won't be restarted.
config-file
Syntax
teku migrate-database --config-file=<FILE>
Example
teku migrate-database --config-file=/home/me/me_node/config.yaml
Environment variable
TEKU_CONFIG_FILE=/home/me/me_node/config.yaml
Path to the YAML configuration file. The default is none
.
data-base-path
, data-path
Syntax
teku migrate-database --data-base-path=<PATH>
Example
teku migrate-database --data-base-path=/home/me/me_node
Environment variable
TEKU_DATA_BASE_PATH=/home/me/me_node
Configuration file
data-base-path: "/home/me/me_node"
Path to the Teku data directory. The default directory is OS-dependent:
- macOS:
~/Library/teku
- Unix/Linux:
$XDG_DATA_HOME/teku
if$XDG_DATA_HOME
is set; otherwise~/.local/share/teku
- Windows:
%localappdata%\teku
The default Docker image location is /root/.local/share/teku
.
data-beacon-path
Syntax
teku migrate-database --data-beacon-path=<PATH>
Example
teku migrate-database --data-beacon-path=/home/me/me_node
Environment variable
TEKU_DATA_BEACON_PATH=/home/me/me_node
Configuration file
data-beacon-path: "/home/me/me_node"
Path to the beacon node data. The default is <data-base-path>/beacon
where <data-base-path>
is specified using --data-base-path
.
network
Syntax
teku migrate-database --network=<NETWORK>
Example
teku migrate-database --network=mainnet
Environment variable
TEKU_NETWORK=mainnet
Configuration file
network: "mainnet"
Predefined network configuration. Accepts a predefined network name, or file path or URL to a YAML configuration file. See the consensus specification for examples.
The default is mainnet
.
Possible values are:
Network | Chain | Type | Description |
---|---|---|---|
mainnet | Consensus layer | Production | Main network |
minimal | Consensus layer | Test | Used for local testing and development networks |
goerli | Consensus layer | Test | Multi-client testnet |
gnosis | Consensus layer | Production | Network for the Gnosis chain |
holesky | Consensus layer | Test | Multi-client testnet |
sepolia | Consensus layer | Test | Multi-client testnet |
chiado | Consensus layer | Test | Gnosis testnet |
lukso | Consensus layer | Production | Network for the Lukso chain |