[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757570#comment-17757570 ]
Doug Rohrer commented on CASSANDRA-18725: ----------------------------------------- Forgot to include the 3.11 Circle run: [https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/175/workflows/7fb4200b-253b-4a48-b1ec-527ab626d83b/jobs/7239/tests] Again, one known failure {testReprepareMixedVersionWithoutReset} https://issues.apache.org/jira/browse/CASSANDRA-18021 > 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 > Components: Test/dtest/java > Reporter: Doug Rohrer > Assignee: Doug Rohrer > Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > Time Spent: 2.5h > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org