You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add --runtime-state-path parameter to support test orchestration
By default state will not be written, and providing
--runtime-state-path will ensure runtime state (API URI, bootstrap
address, and pid) are written to the provided path on startup and
removed from the provided path on shutdown. The details in the written
file support orchestrating nodes for testing:
- pid: check if process is running, stop the process
- uri: connect to the node's API
- bootstrap address: used by other nodes to bootstrap themselves
fs.Float64(TracingSampleRateKey, 0.1, "The fraction of traces to sample. If >= 1, always sample. If <= 0, never sample")
389
389
fs.StringToString(TracingHeadersKey, map[string]string{}, "The headers to provide the trace indexer")
390
390
// TODO add flag to take in headers to send from exporter
391
+
392
+
fs.String(RuntimeStatePathKey, "", "The path to write runtime state to (including uri, bootstrap address and pid). If empty, runtime state will not be written.")
391
393
}
392
394
393
395
// BuildFlagSet returns a complete set of flags for avalanchego
0 commit comments