[
https://issues.apache.org/jira/browse/CASSANDRA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077801#comment-14077801
]
Russell Alexander Spitzer commented on CASSANDRA-7620:
------------------------------------------------------
I definitely see the benefits to explict setting of key ranges but at the same
time I think it's more conceptually simple to keep all the other parameters the
same and only change the seed to get different data. If we aren't going to
allow user specification though we should probably pull it out of the config
file as well.
As an aside related to seed specification, as it is stress currently
non-deterministic. I think we may want to force repeated runs with the same
parameters to generate the same data. I could start another ticket for this if
that's an issue for anyone else.
For example running
{code}
./bin/cassandra-stress user "ops(insert=1)" profile=cqlstress-example.yaml
n=1000 no_warmup -rate threads=200
Select * from stresscql.testtypes # (2097 rows)
./bin/cassandra-stress user "ops(insert=1)" profile=cqlstress-example.yaml
n=1000 no_warmup -rate threads=200
Select * from stresscql.testtypes # (2954 rows)
{code}
I think most users would expect that you would generate the exact same data
with the same command so it may be worthwhile to modify this.
> 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)
