cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10109) Windows dtest 3.0: failures
Date Tue, 18 Aug 2015 00:02:45 GMT


Stefania commented on CASSANDRA-10109:

This is bad news. As far as I understand the documentation, this means that on Windows we
cannot list files in a directory atomically, third paragraph [here|].

So we could list some sstable temporary files but not the txn log file, later they get deleted
along with their txn log file by a racing thread, and if we fail to list the txn log file
we classify these sstable files incorrectly as final files. However, these files shouldn't
exist any longer since the txn log is deleted last, so this would result in NoSuchFileExceptions
when trying to read the files.

I think we should check that all final files exist before returning them and repeat the process
in case some files no longer exist. This should only be done when we don't have atomic listing.

[~benedict] do you think this would be enough or do you see other potential races?

> Windows dtest 3.0: failures
> ---------------------------------------
>                 Key: CASSANDRA-10109
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>              Labels: Windows
>             Fix For: 3.0.x
> 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