[
https://issues.apache.org/jira/browse/CASSANDRA-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064178#comment-15064178
]
Carl Yeksigian commented on CASSANDRA-10863:
--------------------------------------------
I have a new [dtest
branch|https://github.com/carlyeks/cassandra-dtest/tree/10863] which switched
from using {{lsof}} to the jmx {{connectedThriftClients}}, which was also non-0
in the original ticket (CASSANDRA-6546).
A [3.0
branch|http://cassci.datastax.com/view/Dev/view/carlyeks/job/carlyeks-ticket-10863-3.0-dtest/lastSuccessfulBuild/testReport/thrift_hsha_test/ThriftHSHATest/test_closing_connections/history/]
on cassci looks OK.
> HSHA test_closing_connections test still flaps on 3.0
> -----------------------------------------------------
>
> Key: CASSANDRA-10863
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10863
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Carl Yeksigian
> Fix For: 3.0.x
>
>
> The problem reported in CASSANDRA-10570 still seems to be happening on
> CassCI, as recently as a couple days ago:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/433/
> [~carlyeks] The fix in #10570 was to increase how long we'd sleep in the
> tests. Should we just bump it up further, or does this make you suspect a
> larger problem here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
