KIP-311: reserve cross-type slots via own-mesh peer-target caps#122
Merged
Conversation
CN-to-CN and EN-to-EN peerTargets change from infinity to `M - cross-reservation`, so a node's own-type mesh cannot consume every connection and starve the CN<->EN link. The reservation now holds regardless of how MaxPhysicalConnections is configured, rather than relying on implicit sizing (MaxNodeCount + reservation). Cross-type reservation values are documented as operator-configurable defaults. Rejected: keep peerTargets[CN][CN]=infinity and reserve EN room only via MaxPhysicalConnections sizing | breaks under undersized maxconnections Confidence: high Scope-risk: narrow Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
9 tasks
hyunsooda
changed the title
ian0371
approved these changes
Jun 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposed changes
Own-mesh
peerTargets(CN↔CN, EN↔EN) change from∞toM − cross-type reservation, so a node's own-type mesh can no longer consume every connection slot and starve the CN↔EN link.∞; the CN↔EN reservation was implicit, relying on operators sizingM ≥ MaxNodeCount + peerTargets[CN][EN].M − reservation, so cross-type slots are explicitly reserved regardless of howMaxPhysicalConnectionsis configured. In the recommended config the cap never binds (identical to∞); it only adds a guaranteed floor whenmaxconnectionsis undersized.Types of changes
Checklist
Related issues