Delay before reconnecting to the worker NET-883#207
Merged
Conversation
05e964d to
d8829ba
Compare
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
d8829ba to
73a5266
Compare
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
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
The portal was burning a lot of CPU and running OOM. Root cause: when many workers refuse the connections (NET-883), each refusal closes the connection and
on_connection_closedre-dialed instantly. The dial→refuse→redial loop ran at QUIC-handshake speed —transport_libp2p_identify_errors_totalclimbed ~4,100/sec — churning anon heap that jemalloc retained until OOM.Fix
Add a flat per-peer reconnect cooldown between a connection close and its redial. Default 30s, override via
RECONNECT_COOLDOWN_SEC.