[
https://issues.apache.org/jira/browse/CASSANDRA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077821#comment-14077821
]
Russell Alexander Spitzer commented on CASSANDRA-7620:
------------------------------------------------------
I think the issue is that different clustering columns are being generated, |
{code}
./bin/cassandra-stress user "ops(insert=1)" profile=cqlstress-example.yaml
n=1000 no_warmup -key populate=1..1000 -rate threads=200
cqlsh:stresscql> SELECT count(*) FROM typestest ;
count
-------
3052
(1 rows)
./bin/cassandra-stress user "ops(insert=1)" profile=cqlstress-example.yaml
n=1000 no_warmup -key populate=1..1000 -rate threads=200
cqlsh:stresscql> SELECT count(*) FROM typestest ;
count
-------
4334
(1 rows)
{code}
Should we swap this ticket to be "Remove seed from user stress"? Or should I
make a new ticket for that
> Allow user stress commands to specify the seed on the command line
> ------------------------------------------------------------------
>
> Key: CASSANDRA-7620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7620
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Russell Alexander Spitzer
> Assignee: Russell Alexander Spitzer
> Priority: Trivial
> Attachments: CASSANDRA-7620-2.1.patch
>
>
> Although I don't want to add to parameter bloat, it would be really useful if
> the seed for a particular profile could be set on the command line. This
> makes it easier to run the same command with many different seed settings
> without modifying the profile file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
