[
https://issues.apache.org/jira/browse/CASSANDRA-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701474#comment-14701474
]
Benedict commented on CASSANDRA-10109:
--------------------------------------
bq. Are we currently discussing having and maintaining 2 separate execution
paths for Linux and other OS' when it comes to the txn logs and sstable
management?
bq. Are we offering the same guarantees of consistency and safety to a user's
data on Windows (and OSX) as we are on Linux?
ish.
It's worth noting that we're here worrying about situations that can already
occur but we do not as yet try to deal with. i.e. performing listing of the
sstables on disk during a period that Cassandra is live and actively mutating
this state. So really, your worry is misplaced. It should be worrying about the
status quo, which makes no attempt of any guarantees of providing a consistent
snapshot.
We're also very likely to be able to offer this still, just a little more
unpleasantly on Windows and OSX, however we also are very likely to use the
same basic codepath for both, with the expectation that on Linux it will just
complete first time, whereas on OSX or Windows it may spin a few times trying
to find a consistent view, but probably will not here either, since hitting
this kind of race condition is unlikely. And even if we do, it probably does
not cause anything catastrophic since, as I say, we currently make no such
efforts and the world hasn't collapsed.
> Windows dtest 3.0: ttl_test.py failures
> ---------------------------------------
>
> Key: CASSANDRA-10109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10109
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Joshua McKenzie
> Assignee: Stefania
> Labels: Windows
> Fix For: 3.0.x
>
>
> ttl_test.py:TestTTL.update_column_ttl_with_default_ttl_test2
> ttl_test.py:TestTTL.update_multiple_columns_ttl_test
> ttl_test.py:TestTTL.update_single_column_ttl_test
> 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\dtest.py", line 532, in tearDown
> raise AssertionError('Unexpected error in %s node log: %s' % (node.name,
> errors))
> AssertionError: Unexpected error in node1 node log: ['ERROR [main] 2015-08-17
> 16:53:43,120 NoSpamLogger.java:97 - 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
(v6.3.4#6332)
