cassandra-commits mailing list archives

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

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

Ariel Weisberg commented on CASSANDRA-9347:
-------------------------------------------

I think you have to do option #2 right now. It's not designed to run indefinitely because
it doesn't discard log segments as it goes. That is something I would like to fix. Maybe also
look into exercising commit log archiving as well? 

I am still on the fence as to whether this is the right way to test this subsystem, but we
made changes for 2.2 so we should do what we can now.

> 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: Ryan McGuire
>             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