near-dyn-configs

Dynamic config helpers for the NEAR codebase.

This crate contains utilities that allow to reconfigure the node while it is running.

How to:

Logging and tracing

Logging options are controlled by the rust_log entry in the ${NEAR_HOME}/log_config.json. The example entry may look like

{
    "rust_log": "transaction-generator=info,garbage_collection=trace"
}

where the transaction-generator and garbage_collection are the targets in the tracing calls.

Tracing options are similarly controlled by the opentelemetry field:

    "opentelemetry": "client=debug,chain=debug,stateless_validation=debug,info"

Apply changes

Make changes to ${NEAR_HOME}/log_config.json and send SIGHUP signal to the neard process

kill -HUP $(pidof neard)

Other config values

Makes changes to config.json and send SIGHUP signal to the neard process.

Fields of config that can be changed while the node is running:

• expected_shutdown: the specified block height neard will gracefully shutdown at.

Changing other fields of config.json

The changes to other fields of config.json will be silently ignored as long as config.json remains a valid json object and passes internal validation.

Please be careful about making changes to config.json because when a node starts (or restarts), it checks the validity of the config files and crashes if detects any issues.