You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems gossipsub protocol keeps active substreams for connections that exists outside the gossip-mesh. As a result, connections remain alive even after idle_connection_timeout.
This functionality appears to have changed from version v0.52.0, where gossip kept connections alive only within the mesh. Commits with relevant updates: fafa6bc and fcd410a
Expected behavior
Gossipsub protocol should keep connections alive, but exclusively for peers within the mesh
Actual behavior
Gossipsub protocol keeps all connections alive
Relevant log output
No response
Possible Solution
Ignore gossip substreams in the connection-keep-alive algorithm. Use libp2p_swarm::stream::Stream::ignore_for_keep_alive for gossip inbound and outbound substreams.
Version
0.53.1
Would you like to work on fixing this bug ?
Maybe
The text was updated successfully, but these errors were encountered:
Summary
It seems
gossipsub
protocol keeps active substreams for connections that exists outside the gossip-mesh. As a result, connections remain alive even afteridle_connection_timeout
.This functionality appears to have changed from version
v0.52.0
, where gossip kept connections alive only within the mesh. Commits with relevant updates: fafa6bc and fcd410aExpected behavior
Gossipsub
protocol should keep connections alive, but exclusively for peers within the meshActual behavior
Gossipsub
protocol keeps all connections aliveRelevant log output
No response
Possible Solution
Ignore gossip substreams in the
connection-keep-alive algorithm
. Uselibp2p_swarm::stream::Stream::ignore_for_keep_alive
for gossip inbound and outbound substreams.Version
0.53.1
Would you like to work on fixing this bug ?
Maybe
The text was updated successfully, but these errors were encountered: