You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andreas Flinck (JIRA)" <ji...@apache.org> on 2015/03/11 16:11:38 UTC
[jira] [Updated] (CASSANDRA-8948) cassandra-stress does not honour
consistency level (cl) parameter when used in combination with user command
[ https://issues.apache.org/jira/browse/CASSANDRA-8948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Flinck updated CASSANDRA-8948:
--------------------------------------
Summary: cassandra-stress does not honour consistency level (cl) parameter when used in combination with user command (was: consistency level (cl) parameter is not honoured in combination with user command)
> cassandra-stress does not honour consistency level (cl) parameter when used in combination with user command
> ------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8948
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Andreas Flinck
> Priority: Minor
>
> The stress test tool does not honour "cl" parameter when used in combination with the "user" command. Consistency level will be default ONE no matter what is set by "cl=".
> Works fine with "write" command.
> How to reproduce:
> 1. Create a suitable yaml-file to use in test
> 2. Run e.g. {code}./cassandra-stress user profile=./file.yaml cl=ALL no-warmup duration=10s ops\(insert=1\) -rate threads=4 -port jmx=7100{code}
> 3. Observe that cl=ONE in trace logs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)