Skip to content

Conversation

@jxs
Copy link
Member

@jxs jxs commented Oct 17, 2025

Description

Split off from #6183, to quote:

I noticed two issues during testing.

We allow our mesh to grow greater than mesh_n_high, intentionally
This looks like its intentional but I can't recall why we would have added it. I think its counter-intuitive to allow our mesh to grow larger than the specified parameter. I suspect we added it to prevent our mesh from being filled with inbound peers and potentially being eclipsed. I suspect the best approach here is to remove inbound peers in the mesh maintenance rather than exceeding the mesh_n_high configuration.

@jxs jxs force-pushed the gossipsub-fix-mesh-low branch from 18efa2c to 3176449 Compare October 18, 2025 00:22
@jxs jxs force-pushed the gossipsub-fix-mesh-low branch from 3d1f64c to 9a347c4 Compare October 22, 2025 12:41
@jxs jxs force-pushed the gossipsub-fix-mesh-low branch from 9a347c4 to 4fa65cc Compare October 22, 2025 13:04
@jxs jxs force-pushed the gossipsub-fix-mesh-low branch from 4fa65cc to 211eb44 Compare October 23, 2025 14:53
@jxs jxs changed the title fix(gossisub): prevent mesh exceeding mesh_n_high when handling GRAFTs fix(gossisub): prevent mesh exceeding mesh_n_high Oct 23, 2025
Copy link
Contributor

@AgeManning AgeManning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah nice. This looks good to me

@jxs jxs added the send-it label Oct 24, 2025
@mergify mergify bot added the queued label Oct 24, 2025
@mergify mergify bot merged commit e0e6037 into libp2p:master Oct 24, 2025
70 checks passed
@mergify mergify bot removed the queued label Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants