fix(network): stop reth liveness probe from killing consistency recovery#750
Open
bussyjd wants to merge 1 commit into
Open
fix(network): stop reth liveness probe from killing consistency recovery#750bussyjd wants to merge 1 commit into
bussyjd wants to merge 1 commit into
Conversation
The upstream ethereum-node chart's reth subchart defaults to a tcp liveness probe on p2p (30303) with failureThreshold 3 (~12 min grace). Reth keeps that port closed while running post-crash check_consistency recovery, which can take far longer on a large datadir — so the kubelet SIGKILLs it mid-recovery, each kill adds more drift to heal on the next start, and the node crash-loops permanently (observed: 637 restarts, ~129k blocks of StoragesHistory drift). Override the probe with failureThreshold 10000 so it effectively never fires; a genuinely dead reth exits the container on its own. Scoped to reth only — geth/nethermind/besu probe http-rpc and erigon probes metrics, none of which close during recovery. Claude-Session: https://claude.ai/code/session_01VLQSsnH9WdAsnVYGTd2omr
bussyjd
force-pushed
the
fix/reth-liveness-recovery
branch
from
5766fdf to
f77eb81
Compare
OisinKyne
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
obol network install ethereum(reth) can enter a permanent crash loop after any unclean shutdown. Observed live: 637 restarts on a mainnet full node.The upstream
ethereum-nodechart's reth subchart defaults to a TCP liveness probe on the p2p port (30303) withfailureThreshold: 3/periodSeconds: 120— ~12 minutes of grace. Reth keeps that port closed while running post-crashcheck_consistencyrecovery, which routinely takes longer than that on a large datadir. So:Fix
Override the reth liveness probe in the ethereum helmfile with
failureThreshold: 10000(effectively never fires). A genuinely dead reth exits the container on its own, so the probe adds nothing. The upstream chart has nostartupProbesupport, so a values override is the only lever.Scoped to reth only: geth/nethermind/besu probe
http-rpcand erigon probesmetrics, none of which close during recovery.Verification
helmfile templaterender of the ethereum helmfile withexecutionClient: reth: reth StatefulSet getslivenessProbe: {tcpSocket: p2p-tcp, failureThreshold: 10000}; lighthouse StatefulSet untouched.https://claude.ai/code/session_01VLQSsnH9WdAsnVYGTd2omr