[
https://issues.apache.org/jira/browse/CASSANDRA-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158324#comment-13158324
]
Sylvain Lebresne commented on CASSANDRA-3520:
---------------------------------------------
I was a bit fast at calling it victory. I was testing with CleanupTest that was
hanging as well, and starting from the same revision, so I assumed that the
problem was the exact same as for CliTest. Turns out setting durable writes
does fix both CleanupTest and AntiEntropyServiceCounterTest, but CliTest is
still hanging (it's now the only one to do so however).
> Unit test are hanging on 0.8 branch
> -----------------------------------
>
> Key: CASSANDRA-3520
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3520
> Project: Cassandra
> Issue Type: Bug
> Components: Tests
> Environment: Linux
> Reporter: Sylvain Lebresne
> Fix For: 0.8.8
>
> Attachments: 0001-Use-durable-writes-for-system-ks.patch
>
>
> As the summary says, the unit test on current 0.8 are just hanging after
> CliTest (it's apparently not the case on windows, but it is on Linux and
> MacOSX).
> Not sure what's going on, but what I can tell is that it's enough to run
> CliTest to have it hang after the test successfully pass (i.e, JUnit just
> wait indefinitely for the VM to exit). Even weirder, it seems that it is the
> counter increment in the CliTest that make it hang, if you comment those
> statement, it stop hanging. However, nothing seems to go wrong with the
> increment itself (the test passes) and it doesn't even trigger anything
> (typically sendToHintedEndpoint is not called because there is only one node).
> Looking at the stack when the VM is hanging (attached), there is nothing
> specific to counters in there, and nothing that struck me at odd (but I could
> miss something). There do is a few thrift thread running (CASSANDRA-3335),
> but why would that only be a problem for the tests in that situation is a
> mystery to me.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
