[
https://issues.apache.org/jira/browse/CASSANDRA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903611#action_12903611
]
Jonathan Ellis commented on CASSANDRA-1430:
-------------------------------------------
this is caused by sstable statistics being written after the flush (see
ssTableWriter.closeAndOpenReader)
is it time to admit that storing sstable info, in sstables, wasn't a good idea?
> Intermittent CL test failures in trunk.
> ---------------------------------------
>
> Key: CASSANDRA-1430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1430
> Project: Cassandra
> Issue Type: Test
> Affects Versions: 0.7 beta 1
> Reporter: Gary Dusbabek
> Fix For: 0.7 beta 2
>
>
> [junit] Testcase: testCleanup(org.apache.cassandra.db.CommitLogTest):
> FAILED
> [junit] 2 != 1
> [junit] junit.framework.AssertionFailedError: 2 != 1
> [junit] at
> org.apache.cassandra.db.CommitLogTest.testCleanup(CommitLogTest.java:69)
> [junit]
> [junit]
> I see this 1-2 times a day.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.