[
https://issues.apache.org/jira/browse/CASSANDRA-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900486#comment-13900486
]
Benedict commented on CASSANDRA-6691:
-------------------------------------
Hi [~xedin],
Unfortunately I screwed up this commit slightly (like most of those I submitted
yesterday...)
The new feature of checking the data returned was correct was simply no-op'ing.
I've updated my repository with the simple fix (and merged with your changes to
trunk).
> Improvements and FIxes to Stress
> --------------------------------
>
> Key: CASSANDRA-6691
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6691
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1
>
>
> There were a couple of minor issues with the new stress:
> 1) The warmup period did not scale up as the cluster size increased
> 2) The mixed workload did not work with CQL
> At the same time, I have introduced a change in behaviour in the way the
> default column values are generated so that they are deterministically based
> on the key. I have then modified read operations to verify that the data they
> fetch is the same as should have been inserted, so that stress does some
> degree of data quality checking at the same time. For the moment the values
> generated never vary for a given key, so this does nothing to test
> consistency, it only tests for corruption.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
