cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9347) Manually run CommitLogStress for 2.2 release
Date Tue, 19 May 2015 15:57:01 GMT

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

Alan Boudreault commented on CASSANDRA-9347:
--------------------------------------------

[~aweisberg] I've setup the jenkins project to run CommitLogStressTest each week. The job
is set to run commit log stress for 2 days on a ec2 machine, which has SSD disk and on a GCE
machine (which has a SAN disk). 

I've been trying to see if/how I could set the archiving in those test but it seems that the
archiving is not triggered the way it would be in a normal node stop/start. If you have any
hints on that, it would be appreciated. It might also require some modifications in that CommitLogStressTest
so it could archive and restore correctly while running. This is the error I see when enabling
archiving: 

{code}
    [junit] Caused by: java.io.IOException: Exception while executing the command: /bin/ln
build/test/cassandra/commitlog/stress/CommitLog-5-1432049832433.log /backup/CommitLog-5-1432049832433.log,
command error Code: 1, command output: /bin/ln: failed to create hard link ‘/backup/CommitLog-5-1432049832433.log’
=> ‘build/test/cassandra/commitlog/stress/CommitLog-5-1432049832433.log’: No such file
or directory
{code}


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

Mime
View raw message