[
https://issues.apache.org/jira/browse/CASSANDRA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077813#comment-14077813
]
Benedict commented on CASSANDRA-7620:
-------------------------------------
bq. 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.
If you specify -key populate=1..1000 you should get deterministic behaviour.
Probably we should default to populate=1..N if only inserts are specified, as I
believe we do for non-user-defined inserts.
bq. If we aren't going to allow user specification though we should probably
pull it out of the config file as well.
Right, this is what I'm suggesting. I'm worried it both doesn't offer enough to
warrant complicating the option list (which is already complex and will grow
further soon), and that if you have multiples stresses running against the same
cluster, using different seeds (accidentally) may give bad results, esp. if
verification of results is turned on (although that currently isn't
implemented, it will be soon)
> 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)
