op-node: default OP_NODE_L2_ENGINE_RPC_TIMEOUT=120s for all OP-stack nodes
op-node's default engine-API RPC timeout is short; on nodes whose EL responds slowly to engine_newPayload/forkChoiceUpdated (e.g. boba-mainnet op-reth pruned during catch-up) op-node times out driving the EL and the execution head freezes while op-node keeps deriving from L1. Raising the engine RPC timeout to 120s prevents this class of stall fleet-wide. Regenerated from env/op/node.env: adds the env var to every op-node service (116 geth + 40 reth + 22 erigon composes); additions only, no other changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -120,6 +120,7 @@ services:
|
||||
- OP_NODE_L1_TRUST_RPC=${ETHEREUM_MAINNET_EXECUTION_TRUST:-false}
|
||||
- OP_NODE_L2_ENGINE_AUTH=/jwtsecret
|
||||
- OP_NODE_L2_ENGINE_RPC=http://mode-mainnet:8551
|
||||
- OP_NODE_L2_ENGINE_RPC_TIMEOUT=120s
|
||||
- OP_NODE_L2_SKIP_SYNC_START_CHECK=true
|
||||
- OP_NODE_LOG_LEVEL=info
|
||||
- OP_NODE_METRICS_ADDR=0.0.0.0
|
||||
|
||||
Reference in New Issue
Block a user