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
When two memberlist instances (using QuicTransport) in the same test case, and node1 joins node2, then, shut down node1, drops node1, and finally brings back node1 by using the same configuration, it will report the error "Address already in use". This may be caused by that the remote (node2) still holds the connection to node1, and the underlying socket address is held by the connection.
Pseudo code:
let n1 = Memberlist::new(...).await.unwrap();let n2 = Memberlist::new(...).await.unwrap();
n1.join(n2).await.unwrap();
n1.shutdown().await.unwrap();drop(n1);let n1 = Memberlist::new(...).await.unwrap();// panic: "Address already in used".
The text was updated successfully, but these errors were encountered:
al8n
changed the title
[BUG]: QuicTransport does not release the port after shutdown the Memberlist
[BUG]: QuicTransport does not release the port after shutdown the Memberlist in test case
Apr 14, 2024
When two memberlist instances (using
QuicTransport
) in the same test case, and node1 joins node2, then, shut down node1, drops node1, and finally brings back node1 by using the same configuration, it will report the error "Address already in use". This may be caused by that the remote (node2) still holds the connection to node1, and the underlying socket address is held by the connection.Pseudo code:
The text was updated successfully, but these errors were encountered: