Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: QuicTransport does not release the port after shutdown the Memberlist in test case #39

Open
al8n opened this issue Apr 9, 2024 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@al8n
Copy link
Owner

al8n commented Apr 9, 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:

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".
@al8n al8n added the bug Something isn't working label Apr 9, 2024
@al8n al8n self-assigned this Apr 9, 2024
@al8n al8n added this to the 0.2.0 milestone Apr 9, 2024
@al8n 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant