[
https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770521#comment-17770521
]
Jon Meredith commented on CASSANDRA-18725:
------------------------------------------
Reran against 5.0 branch. Clean runs.
java11_separate_tests
https://app.circleci.com/pipelines/github/jonmeredith/cassandra/959/workflows/99204b8b-40a2-4ceb-becd-df6d3d0afdc2
java17_separate_tests
https://app.circleci.com/pipelines/github/jonmeredith/cassandra/959/workflows/a1e6df8b-b61c-4359-aaef-9b3ff08ebbcd
> 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.17, 4.0.12, 4.1.4, 5.0-alpha, 5.x
>
> Time Spent: 3h 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
