-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add a close method to AsyncMultiMap #2270
Conversation
This allows cluster managers to free resources they use to maintain the state. Needed for vert-x3/issues#316 Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
@vietj PTAL |
how did it work before without a close method ? |
can we try instead to use java refs ? we have several places in vertx where we do that for better usability |
|
Sorry I can't see what you mean... :( |
weak references, look at NetClientImpl |
Not sure how we could. We have to unregister listeners on the HZ map and
the ISPN cache. See the related cluster manager PRs
2018-01-10 16:40 GMT+01:00 Julien Viet <notifications@github.com>:
… weak references, look at NetClientImpl
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2270 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABbltt_R65ZUl5ro0jLWWaLO3zVY6YJbks5tJNn6gaJpZM4RZa_H>
.
|
I think you can on the map proxy itself as only the client has a ref to it, can't you ? |
Sorry I don't understand. In any case, HZ or ISPN may still hold resources
related to the listener. So unregistering it seems mandatory
2018-01-10 16:52 GMT+01:00 Julien Viet <notifications@github.com>:
… I think you can on the map proxy itself as only the client has a ref to
it, can't you ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2270 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABblth_wv49rMIfcs-AX7rou89HzBV5Hks5tJNyxgaJpZM4RZa_H>
.
|
@vietj can you take another look before we close the 3.5.1 round? Thanks |
vert-x3/issues#316 closed (won't fix) |
This allows cluster managers to free resources they use to maintain the state.
Needed for vert-x3/issues#316