Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <12302617.42881282947713985.JavaMail.jira@thor>
Date: Fri, 27 Aug 2010 18:21:53 -0400 (EDT)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1430) Intermittent CL test failures in
 trunk.
In-Reply-To: <8525919.559791282750816053.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903675#action_12903675 ] 

Gary Dusbabek commented on CASSANDRA-1430:
------------------------------------------

>is it time to admit that storing sstable info, in sstables, wasn't a good idea?
What if statistics operations ran on its own stage that could be halted at critical moments (flushing, for example).


> 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.