[CASSANDRA-10109] Windows dtest 3.0: ttl_test.py failures

• Type: Sub-task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.0 rc1
• Component/s: Legacy/Local Write-Read Paths
• Labels: Windows
• Assignee: Stefania Alborghetti
• Reporter: Joshua McKenzie

Authors

Stefania Alborghetti

Reviewers

Benedict Elliott Smith

• Created: 17/Aug/15 20:59
• Updated: 16/Apr/19 09:31
• Resolved: 08/Sep/15 11:00

Description

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:

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']

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.

Issue Links

• blocks: CASSANDRA-10035 Windows utest 3.0: TransactionLogsTest failure
• duplicates: CASSANDRA-10210 Windows utest 3.0: org.apache.cassandra.io.sstable.SSTableLoaderTest.testLoadingIncompleteSSTable
• is broken by: CASSANDRA-7066 Simplify (and unify) cleanup of compaction leftovers
• is duplicated by: CASSANDRA-10105 Windows dtest 3.0: TestOfflineTools failures
• is duplicated by: CASSANDRA-10107 Windows dtest 3.0: TestScrub and TestScrubIndexes failures
• links to: 3.0 patch