cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3520) Unit test are hanging on 0.8 branch
Date Fri, 25 Nov 2011 15:57:40 GMT


Sylvain Lebresne commented on CASSANDRA-3520:

btw, how sure are we that using non-durable writes for the system keyspace is a good idea?
It doesn't seem great for hints at least. Moreover on 1.0, when will the CF be flushed if
durable_writes is false unless we do a manual flush?
> Unit test are hanging on 0.8 branch
> -----------------------------------
>                 Key: CASSANDRA-3520
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message