Expected Behavior
When I set persistent peers, they should be kept connected.
Every now and then, if a persistent peer is disconnected, it should evict other peer and reconnect.
Current Behavior
When you set max conns to 1 and outgoing conns to 1, peer is connected too early, causing errors like:
2025-01-31T14:51:51.511918816Z ERROR Cannot send bytes to unknown channel channel=32 module=p2p peer={"Hostname":"54.202.218.46","NodeID":"5711bbd0e0d6cdefdf3c1565e3808a37d82e457a","Path":"","Port":26656,"Protocol":"mconn"}
2025-01-31T14:51:51.515846805Z ERROR peer failure endpoint={} err="sending message timed out" module=p2p peer=5711bbd0e0d6cdefdf3c1565e3808a37d82e457a
After that, system connects to another node. This causes all "slots" to be busy so connection is not retried.
Expected Behavior
When I set persistent peers, they should be kept connected.
Every now and then, if a persistent peer is disconnected, it should evict other peer and reconnect.
Current Behavior
When you set max conns to 1 and outgoing conns to 1, peer is connected too early, causing errors like:
After that, system connects to another node. This causes all "slots" to be busy so connection is not retried.