[
https://issues.apache.org/jira/browse/CASSANDRA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077637#comment-14077637
]
Benedict commented on CASSANDRA-7620:
-------------------------------------
tbh, thinking about it a little bit, I'm no longer convinced a user-specified
seed makes any sense. The seed is used to generate the partition-key seeds, and
to generate the initial column seeds. However you can achieve essentially the
same effect by choosing a different key range with your key parameter, i.e.
\-key dist=gauss(1M..2M) will generate completely different values to \-key
dist=gauss(0..1M). The benefit of doing it this way is that two stress commands
operating over an overlapping range will continue to generate the same data for
the overlapping partitions, so we can never have two stress clients clashing
with each other. I can't think of a benefit to separately specifying a seed on
top.
> 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)
