You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Doug Rohrer (Jira)" <ji...@apache.org> on 2023/08/04 13:11:00 UTC
[jira] [Created] (CASSANDRA-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
Doug Rohrer created CASSANDRA-18725:
---------------------------------------
Summary: IsolatedJMX should not release all TCPEndpoints on instance shutdown
Key: CASSANDRA-18725
URL: https://issues.apache.org/jira/browse/CASSANDRA-18725
Project: Cassandra
Issue Type: Improvement
Reporter: Doug Rohrer
In the original implementation of the JMX feature, we fixed some memory leaks by clearing some internal state in Java’s TCPEndpoint. However, that implementation was overly aggressive and cleared the whole map, vs. just removing the endpoints created by the individual instances. This causes issues when you remove a node from the cluster (as all of the endpoints are cleared, not just the ones in use by that instance).
In stead, we should check if the endpoint was created by the instance in question and only remove it if it was.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org