Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 4 Jun 2015 12:44:39 +0000 (UTC)
From: "Alan Boudreault (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12828916.1431370631000.10678.1433421879437@Atlassian.JIRA>
In-Reply-To: <JIRA.12828916.1431370631000@Atlassian.JIRA>
References: <JIRA.12828916.1431370631000@Atlassian.JIRA>
 <JIRA.12828916.1431370631784@arcas>
Subject: [jira] [Resolved] (CASSANDRA-9347) Manually run CommitLogStress for
 2.2 release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Boudreault resolved CASSANDRA-9347.
----------------------------------------
    Resolution: Fixed

> Manually run CommitLogStress for 2.2 release
> --------------------------------------------
>
>                 Key: CASSANDRA-9347
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9347
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ariel Weisberg
>            Assignee: Alan Boudreault
>              Labels: qa-resolved
>             Fix For: 2.2.x
>
>
> Commitlog stress runs each test for 10 seconds based on a constant. Might be worth raising that to get the CL doing a little bit more work.
> Then run it in a loop on something with a fast SSD and something with a slow disk for a few days and see if it fails.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)