[ 
https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754118#comment-17754118
 ] 

Doug Rohrer commented on CASSANDRA-18725:
-----------------------------------------

So far seeing nothing but known jvm-dtest failures in Circle. Given the changes 
are isolated to the in-jvm dtest framework I'm focusing on those failures as it 
shouldn't touch anything else.

4.0:
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/167]
{{testFailingMessage[VALIDATION_REQ/parallel/true]}}
https://issues.apache.org/jira/browse/CASSANDRA-18366

4.1:
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/168]
{{mixedModeReadColumnSubsetDigestCheck}}
https://issues.apache.org/jira/browse/CASSANDRA-18158

5.0:
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/169]
Rerunning J17 as CircleCI said there was an infrastructure failure somehow - 
see 
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/169/workflows/25ccc721-4497-4074-979c-28c92950bff0/jobs/6657]
Java 11 all passed:
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/169/workflows/e5b59a02-7d4e-4ed7-8f62-37c9a33bcb6a]

Trunk:
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/170/workflows/689e6e3e-47a4-4855-8fcb-e95e9da7ea02]
Java 11 and 17 dtests all pass

> 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, 4.1.x, 5.0, 5.1
>
>          Time Spent: 50m
>  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]

Reply via email to