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

Benedict commented on CASSANDRA-8503:
-------------------------------------

I would quite like to see us also generate some profiles and cluster configs 
specifically designed to elicit failure scenarios. Perhaps in conjunction with 
some stress enhancements specifically designed to prevent it knocking a server 
over, but keep it under as much load as possible to tease out unexpected 
behaviour.

For instance random interleaving of all operation types (including range 
queries, counters, etc) with more compaction (smaller LCS tables, smaller 
preemptive reopen interval). Then over time expand this testing to include 
periodically taking down servers, bootstrap new ones, etc. it would be great to 
occupy our test clusters with these tests automatically during any unused 
performance testing time. It seems without this we lack robust acceptance 
testing. 

> Collect important stress profiles for regression analysis done by jenkins
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8503
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8503
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Ryan McGuire
>            Assignee: Ryan McGuire
>         Attachments: inmemory.yaml, ycsb.yaml
>
>
> We have a weekly job setup on CassCI to run a performance benchmark against 
> the dev branches as well as the last stable releases.
> Here's an example:
> http://cstar.datastax.com/tests/id/8223fe2e-8585-11e4-b0bf-42010af0688f
> This test is currently pretty basic, it's running on three nodes, with a the 
> default stress profile. We should crowdsource a collection of stress profiles 
> to run, and then once we have many of these tests running we can collect them 
> all into a weekly email.
> Ideas:
>  * Timeseries (Can this be done with stress? not sure)
>  * compact storage
>  * compression off
>  * ...



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

Reply via email to