IOBalancer keeps references of all the socket reader/writers but when destroying the connection they release the references for only the ones which has endpoints.
It could be seen from the image below that socket writers consume %77 of the total memory after all the connections to hazelcast are destroyed.
If the connection is destroyed and removed from active connections, i…
…t should be removed from iobalancer regardless of connection endpoint. Fixes #6199
good finding 👍
we're seeing another memory leak in IOBalancer in v3.6 - Socket readers/writers are building up in LoadTracker.lastEventCounter. They are getting added to the ItemCounter by updateNewWorkingImbalance but the handler is not removed from the ItemCounter when removeHandler is called.
Can we re-open this issue or should I open a new one?
I am working on a reproducer for your case.
Thanks @mahileeb issue has been fixed and the fix will be available on 3.6.2 and 3.7