cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10109) Windows dtest 3.0: failures
Date Thu, 03 Sep 2015 10:58:47 GMT


Benedict commented on CASSANDRA-10109:

bq. So what do we do with this final corrupt record then: is it "UNKNOWN", which means transaction
always in progress

It's only in progress if all of the other files are present, in which case treating it as
such seems completely safe. The worst case scenario I can see is a transaction that's in the
process of being committed, we fail to read the commit record, and see all the old files are
present, filter out the new files, and then the old files get deleted before the client uses
them. But as discussed this is always a risk, no matter how we do things. Attempting to parse
corrupted records, on the other hand, seems a little worrisome to me. What if it's corrupted
due to disk failure mid-write, and the transaction is actually being aborted? Incredibly unlikely,
I'll grant, but there are probably other failure scenarios.

> Windows dtest 3.0: failures
> ---------------------------------------
>                 Key: CASSANDRA-10109
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>            Assignee: Stefania
>              Labels: Windows
>             Fix For: 3.0.0 rc1
> Errors locally are different than CI from yesterday. Yesterday on CI we have timeouts
and general node hangs. Today on all 3 tests when run locally I see:
> {noformat}
> Traceback (most recent call last):
>   File "c:\src\cassandra-dtest\", line 532, in tearDown
>     raise AssertionError('Unexpected error in %s node log: %s' % (, errors))
> AssertionError: Unexpected error in node1 node log: ['ERROR [main] 2015-08-17 16:53:43,120 - This platform does not support atomic directory streams (SecureDirectoryStream);
race conditions when loading sstable files could occurr']
> {noformat}
> This traces back to the commit for CASSANDRA-7066 today by [~Stefania] and [~benedict].
 Stefania - care to take this ticket and also look further into whether or not we're going
to have issues with 7066 on Windows? That error message certainly *sounds* like it's not a
good thing.

This message was sent by Atlassian JIRA

View raw message