fix: cap pending connection backlog #1993
                
     Merged
            
            
          
  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
Nodes were experiencing unbounded growth in pending connection targets, with
pending_addsincreasing indefinitely (e.g., 2831 → 2855 → 2879 → 2903 → 2927) even when unable to establish new connections.From the logs:
This represents a memory leak where the
pending_conn_addsBTreeSet grows without bound.Root Cause
The connection maintenance loop:
live_tx)Solution
Added
calculate_allowed_connection_additions()function that:max_connectionslimit based on effective connectionsmin_connections, limits additions to deficit neededExample Scenarios
Healthy state (1 connection, 0 pending, need 25 min):
Backlog exists (1 connection, 24 pending, need 25 min):
At capacity (1 connection, 2831 pending, max 200):
Testing
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com