Understanding nodeos state_history_plugin

bitjh · January 20, 2022, 7:48am

Hello,

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:

Docs

xaviercr · January 23, 2022, 8:07pm

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

github.com

eoscostarica/sample-nodeos-configs/blob/main/peering/config/config.ini

# Peering Node Example Config 
agent-name = <agent>  # set agent name

plugin = eosio::chain_plugin
plugin = eosio::net_plugin

chain-threads = 8
net-threads = 8

# Chain Plugin
wasm-runtime = eos-vm
eos-vm-oc-enable = 1
eos-vm-oc-compile-threads = 4
contracts-console = false
abi-serializer-max-time-ms = 2000
chain-state-db-size-mb = 16384
chain-state-db-guard-size-mb = 128
reversible-blocks-db-size-mb = 1024
reversible-blocks-db-guard-size-mb = 2

This file has been truncated. show original

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