EOSCommunity.org Forums

Understanding nodeos state_history_plugin


Despite using a snapshot, my node is currently at block number 6000 which means it will takes ages to sync to the latest block.

There’s probably a configuration issue and many things happening under the hood that I don’t understand.

For starters, what does the state_history_plugin bring to the table? (Link to doc at the end of this message). I don’t really understand so any layman explanation would be very welcome.

Our configuration file config.ini uses this plugin along with filter-on settings. From what I gather we only need information related to our accounts, not the whole blockchain.

Here’s the command used to start the node:

exec nodeos \
    --disable-replay-opts \
    -d /node/data \
    --config-dir /node/config \
    --snapshot $SNAPSHOT_BIN

And essentially config.ini

plugin = eosio::chain_api_plugin
plugin = eosio::state_history_plugin
plugin = eosio::chain_plugin
plugin = eosio::http_plugin
plugin = eosio::net_plugin
plugin = eosio::net_api_plugin

filter-on = someaddress:transfer:


Are you syncing with an updated list of peers?

you can try increasing the number of net_threads have a look at the following sample configs

Also the EOSIO node operator course videos can help you understand more on how to configure a node and the role of the state_history_plugin

take a look at module 3