[
https://issues.apache.org/jira/browse/CASSANDRA-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158465#comment-13158465
]
Jonathan Ellis edited comment on CASSANDRA-3520 at 11/28/11 2:29 PM:
---------------------------------------------------------------------
+1, but can we add a system test w/ a non-durable ks to help prevent
regressions?
Edit: never mind, that's what we're already doing in NoCommitlogSpace, hence
the continuing clitest timeout
was (Author: jbellis):
+1, but can we add a system test w/ a non-durable ks to help prevent
regressions?
> 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, 3520.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
