[jira] Commented: (CASSANDRA-676) stress.py should raise when keys are not found

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on CASSANDRA-676:
----------------------------------

Integrated in Cassandra #316 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/316/])
    add --progress-interval to stress.py.  patch by Brandon Williams; reviewed by jbellis for 
add --keep-going option to continue past exceptions (e.g. to keep hammering server after timeouts start).  check get return value and raise when expected key is not present (cassandra can skip missing keys really really fast but that is not what we want to measure here).  patch by Brandon Williams; reviewed by jbellis for 


> stress.py should raise when keys are not found
> ----------------------------------------------
>
>                 Key: CASSANDRA-676
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-676
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: 0001_raise_on_empty_keys.patch, 0002_configurable_progress_interval.patch
>
>
> Currently, stress.py does not check for results when reading keys.  This makes it easy to get false results if you either don't insert first or have your data dir pointed at the wrong location.  Also, it would be nice if progress of a finer grain than 10s could be reported.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.