[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099525#comment-14099525 ] Benedict commented on CASSANDRA-7468: - FTR, I'm planning to address this once CASSANDRA-7519 is committed, since this is not super-high priority. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Assignee: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: 7468v2.txt, trunk-7468-rebase.patch, trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[
https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092798#comment-14092798
]
Daniel Meyer commented on CASSANDRA-7468:
-
Attempted to run a 24 hour write test with this command:
{code}
$STRESS_CMD write duration=24h tries=20 cl=QUORUM -log file=write_warmup.csv
-node $NODES
{code}
It has now been running for more than 50 hours. Seems like there is an issue
with timing here.
Add time-based execution to cassandra-stress
Key: CASSANDRA-7468
URL: https://issues.apache.org/jira/browse/CASSANDRA-7468
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Matt Kennedy
Assignee: Matt Kennedy
Priority: Minor
Fix For: 2.1.1
Attachments: 7468v2.txt, trunk-7468-rebase.patch, trunk-7468.patch
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093113#comment-14093113 ] Daniel Meyer commented on CASSANDRA-7468: - The problem above is with the command. To get the desired behavior the user must pass in '-rate threads=num_threads'. stress will try to guess a correct thread count every 24 hours. leading to what appears to be an overshoot. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Assignee: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: 7468v2.txt, trunk-7468-rebase.patch, trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[
https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090102#comment-14090102
]
Daniel Meyer commented on CASSANDRA-7468:
-
from the help:
{code}
Usage: user [clustering=DIST(?)] ops(?) [profile=?] [err?] [n?] [n?]
[tries=?] [no_warmup] [ignore_errors] [cl=?] [at-once=?]
OR
Usage: user [clustering=DIST(?)] ops(?) [profile=?] n=? [tries=?] [no_warmup]
[ignore_errors] [cl=?] [at-once=?]
OR
Usage: user [clustering=DIST(?)] ops(?) [profile=?] duration=? [tries=?]
[ignore_errors] [cl=?] [at-once=?]
{code}
Running this commands work:
{code}
./run_stress.sh user no_warmup ops\(insert=1\) profile=$PROFILE n=60 -rate
threads=200 -node 10.1.1.1
{code}
But this does not:
{code}
./run_stress.sh user no_warmup ops\(insert=1\) profile=$PROFILE duration=60
-rate threads=200 -node 10.1.1.1
{code}
Add time-based execution to cassandra-stress
Key: CASSANDRA-7468
URL: https://issues.apache.org/jira/browse/CASSANDRA-7468
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Matt Kennedy
Assignee: Matt Kennedy
Priority: Minor
Fix For: 2.1.1
Attachments: 7468v2.txt, trunk-7468-rebase.patch, trunk-7468.patch
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069268#comment-14069268 ] Matt Kennedy commented on CASSANDRA-7468: - Rebased to trunk. Changed '-d' parameter to '-duration'. Note, running this without the latest DataStax Java driver (2.1-beta2) results in some seemingly extraneous stack traces, but they don't seem to affect functionality. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Assignee: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: trunk-7468-rebase.patch, trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069387#comment-14069387 ] Matt Kennedy commented on CASSANDRA-7468: - Thanks for the review, units are a welcome addition. I'm also relieved you got rid of the countInSeconds boolean to do it. I felt cheap doing it that way :-) Everything else looks good to me. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Assignee: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: 7468v2.txt, trunk-7468-rebase.patch, trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056244#comment-14056244 ] Matt Kennedy commented on CASSANDRA-7468: - I've tried using the n, n method to get timed execution for the last week or so in two different stress testing environments in two cloud providers, unfortunately, the test execution times have run over by a significant amount. The independent timing thread method in the patch gives much more consistent results in terms of executing for the specified execution time. If you don't have any strenuous objections, I would like to see this incorporated. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056645#comment-14056645 ] Benedict commented on CASSANDRA-7468: - Could you rebase? It's changed a bit in the interval Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056654#comment-14056654 ] Matt Kennedy commented on CASSANDRA-7468: - Sure. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Fix For: 2.1.1 Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047559#comment-14047559 ] Benedict commented on CASSANDRA-7468: - This is already pretty easy to specify: If you specify [command] n30 n30, it will run for exactly 30s (well, 30 measurements, which may be slightly longer if there are many cross-cluster pauses). We could add a specific command, but I'm not sure it adds a great deal when it's already easy to do. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047906#comment-14047906 ] Matt Kennedy commented on CASSANDRA-7468: - Hm, that might be easy to do, but it isn't exactly obvious that it's possible. What if the patch were re-worked to expose the -d param to explicitly set duration, but instead of keeping a distinct timer thread, it's internally set to use the same execution path it would have if n30 n30? Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047913#comment-14047913 ] Benedict commented on CASSANDRA-7468: - Well, -d isn't much clearer to me. We could change the n n to s(amples)? s(amples)?, and offer a parallel s(amples)?= also, so that we have a standardised syntax. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047956#comment-14047956 ] Matt Kennedy commented on CASSANDRA-7468: - I picked -d for duration because I think people think of -t being associated with threads. s(amples)= could work, but we'd need to explain that there is a connection between samples and time (specifically a second), that isn't immediately obvious. The current help text for n: Run at least this many iterations before accepting uncertainty convergence doesn't make it clear that an iteration is a second. If you just go with a completely separate parameter for duration, then there's no need to change the language of the other help text just to make the time-based use case more obvious. But it's a simple feature, as long as I can _do_ time based runs, I'm not that fussed about how they get done. Add time-based execution to cassandra-stress Key: CASSANDRA-7468 URL: https://issues.apache.org/jira/browse/CASSANDRA-7468 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Matt Kennedy Priority: Minor Attachments: trunk-7468.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
