You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alan Boudreault (JIRA)" <ji...@apache.org> on 2015/05/13 21:28:01 UTC
[jira] [Commented] (CASSANDRA-9347) Manually run CommitLogStress
for 2.2 release
[ https://issues.apache.org/jira/browse/CASSANDRA-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542512#comment-14542512 ]
Alan Boudreault commented on CASSANDRA-9347:
--------------------------------------------
[~aweisberg] I'm looking to automate that rather than running it manually for 2.2. I will be similar to the DurationTest and could be run weekly or monthly on jenkins. This is what I'm working on:
1. Provide a patch for CommitLogStressTest.java to allow us to specify the run time. (for longer run).
2. Create a new Jenkins CommitLogTest project that will automate the run of this test in a ctool instance.
3. Configure the Jenkins project to launch 2 ctool instances (SSD and NON-SSD) and run a long test for ~2 days.
Does this plan sound good? Let me know if you have anything else in mind.
Question: what would you prefer for the long run tests (2 days):
1. Start only 1 CommitLogStressTest process with very-long run time, which mean that the test will spend many hours on the same compressor test, then pass to the next one.
2. Start many CommitLogStressTest processes *synchronously* with shorter run time. This is mainly just a loop executing the same test multiple times.
> 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)