[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662655#comment-16662655 ] Colin Garcia commented on HBASE-20306: -- Andrew, is it possible for me to use your test cluster? I've ran locally several times and have been unable to replicate the behavior you've described. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651011#comment-16651011 ] Andrew Purtell commented on HBASE-20306: ./bin/hbase ltt -read 100:10 -write 10:100:10 -num_keys 100 > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642281#comment-16642281 ] Colin Garcia commented on HBASE-20306: -- Hey Andrew. I was wondering what test env you were using to run the ltt command? I've been running it locally, and haven't been able to replicate. Thanks in advance > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636299#comment-16636299
]
Colin Garcia commented on HBASE-20306:
--
My output from the latest run, for reference:
{code:java}
~/hbase/bin(master*) » ./hbase ltt -read 100:10 -write 10:100:10 -num_keys
100
{code}
{code:java}
2018-10-02 17:42:15,369 INFO
[MultiThreadedAction-ProgressReporter-1538525614665] util.MultiThreadedAction:
[W:11] Keys=993612, cols=10.9 M, time=00:28:40 Overall: [keys/s= 577,
latency=17.27 ms] Current: [keys/s=566, latency=17.62 ms], wroteUpTo=993597,
wroteQSize=4
2018-10-02 17:42:15,423 INFO
[MultiThreadedAction-ProgressReporter-1538525614699] util.MultiThreadedAction:
[R:10] Keys=9144453, cols=155.6 M, time=00:28:40 Overall: [keys/s= 5314,
latency=0.90 ms] Current: [keys/s=5187, latency=0.95 ms], verified=9144453
2018-10-02 17:42:20,369 INFO
[MultiThreadedAction-ProgressReporter-1538525614665] util.MultiThreadedAction:
[W:11] Keys=996682, cols=10.9 M, time=00:28:45 Overall: [keys/s= 577,
latency=17.26 ms] Current: [keys/s=614, latency=16.24 ms], wroteUpTo=996669,
wroteQSize=2
2018-10-02 17:42:20,425 INFO
[MultiThreadedAction-ProgressReporter-1538525614699] util.MultiThreadedAction:
[R:10] Keys=9171711, cols=156.1 M, time=00:28:45 Overall: [keys/s= 5314,
latency=0.90 ms] Current: [keys/s=5451, latency=0.84 ms], verified=9171711
2018-10-02 17:42:25,369 INFO
[MultiThreadedAction-ProgressReporter-1538525614665] util.MultiThreadedAction:
[W:11] Keys=999798, cols=11.0 M, time=00:28:50 Overall: [keys/s= 577,
latency=17.26 ms] Current: [keys/s=623, latency=16.01 ms], wroteUpTo=999780,
wroteQSize=7
2018-10-02 17:42:25,429 INFO
[MultiThreadedAction-ProgressReporter-1538525614699] util.MultiThreadedAction:
[R:10] Keys=9199696, cols=156.5 M, time=00:28:50 Overall: [keys/s= 5315,
latency=0.90 ms] Current: [keys/s=5597, latency=0.81 ms], verified=9199699
2018-10-02 17:42:30,406 INFO
[MultiThreadedAction-ProgressReporter-1538525614665] util.MultiThreadedAction:
RUN SUMMARY
KEYS PER SECOND [W]: mean=577.53, min=322.00, max=729.00, stdDev=65.36,
50th=586.00, 75th=622.00, 95th=663.00, 99th=711.30, 99.9th=729.00,
99.99th=729.00, 99.999th=729.00
LATENCY [W]: mean=17.05, min=13.00, max=30.00, stdDev=2.42, 50th=16.00,
75th=18.00, 95th=22.00, 99th=27.00, 99.9th=30.00, 99.99th=30.00, 99.999th=30.00
2018-10-02 17:42:30,434 INFO
[MultiThreadedAction-ProgressReporter-1538525614699] util.MultiThreadedAction:
RUN SUMMARY
KEYS PER SECOND [R]: mean=5317.31, min=2953.00, max=6900.00, stdDev=639.58,
50th=5366.00, 75th=5727.00, 95th=6248.65, 99th=6598.89, 99.9th=6900.00,
99.99th=6900.00, 99.999th=6900.00
LATENCY [R]: mean=0.28, min=0.00, max=2.00, stdDev=0.46, 50th=0.00, 75th=1.00,
95th=1.00, 99th=1.00, 99.9th=2.00, 99.99th=2.00, 99.999th=2.00
2018-10-02 17:42:30,783 INFO [main] zookeeper.ReadOnlyZKClient: Close
zookeeper connection 0x31aa3ca5 to localhost:2181
Failed to write keys: 0
2018-10-02 17:42:30,794 INFO [main] zookeeper.ReadOnlyZKClient: Close
zookeeper connection 0x6b44435b to localhost:2181{code}
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Colin Garcia
>Priority: Major
> Labels: beginner
> Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch,
> HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch
>
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636274#comment-16636274 ] Colin Garcia commented on HBASE-20306: -- That's fine, I agree with this assessment. I'm just spitballing to determine what the cause could be. Will keep investigating. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636270#comment-16636270 ] Andrew Purtell commented on HBASE-20306: LTT shuts down without the patch applied, fails to terminate with the patch applied, I'm sorry, I can't commit under these circumstances. If you can't catch it later this week I can try again and drop a stacktrace if it repros > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636264#comment-16636264 ] Colin Garcia commented on HBASE-20306: -- I see. But I don't think the old if/else is right then either. If the reader progress was printing the same status, that would have to mean that there were still worker threads running (as they were formerly the same check), so the old if/else wouldn't have terminated either. This problem might be elsewhere, unrelated to the change but having something to do with how these worker threads are exiting. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch, HBASE-20306.003.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636256#comment-16636256 ] Andrew Purtell commented on HBASE-20306: I don't have the output. Problem was as described. Writer progress thread prints summary and terminates. Reader progress thread continues forever, printing the same (unchanging) status over and over, requiring ^C. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636241#comment-16636241 ] Colin Garcia commented on HBASE-20306: -- [~apurtell] Thanks! Strangely, I ran with the same input and both threads finished (although it took some time). Could there be a race condition here? I don't see how one could run indefinitely as at some point the worker threads will finish, setting isProgressReporter to false. Can you paste what your output was? Fixing the other pieces you suggested now. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635917#comment-16635917 ] Andrew Purtell commented on HBASE-20306: While updating the patch I also think the summary should print the action mode indicator too. See how the progress reporter prints one of R, W, or A. Comes from the task impl specific progressInfo() method I think. The summary line should also print R, W, or A to make it easier to figure out for which action the summary is in regard. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306-branch-1.000.patch, HBASE-20306.000.patch, > HBASE-20306.001.patch, HBASE-20306.002.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635903#comment-16635903
]
Andrew Purtell commented on HBASE-20306:
Patch is not quite ready. When I test with {{./bin/hbase ltt -read 100:10
-write 10:100:10 -num_keys 100}} only one multithreadedaction progress
reporter shuts down. The other continues to run indefinitely, holding up the
process. I think the problem is here:
{code}
@@ -261,7 +285,7 @@ public abstract class MultiThreadedAction {
}
public void waitForFinish() {
-while (numThreadsWorking.get() != 0) {
+while (isProgressReporterRunning) {
Threads.sleepWithoutInterrupt(1000);
}
close();
{code}
I also attached a branch-1 port.
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Colin Garcia
>Priority: Major
> Labels: beginner
> Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch,
> HBASE-20306.002.patch
>
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635823#comment-16635823 ] Andrew Purtell commented on HBASE-20306: Sorry for dropping this. I think the current patch looks good. There are two line length checkstyle warnings but we don't need to do another round of review, I can fix those at commit. Let me see about getting this in today. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch, > HBASE-20306.002.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614186#comment-16614186
]
Hadoop QA commented on HBASE-20306:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
12s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
13s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
48s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
11s{color} | {color:red} hbase-server: The patch generated 2 new + 8 unchanged
- 0 fixed = 10 total (was 8) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
7s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
10m 20s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}122m
33s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}163m 53s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-20306 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12939616/HBASE-20306.002.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux e6218759bd46 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 5d14c1af65 |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HBASE-Build/14410/artifact/patchprocess/diff-checkstyle-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/14410/testReport/ |
| Max. process+thread count | 5232 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console output |
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614096#comment-16614096
]
Colin Garcia commented on HBASE-20306:
--
Thanks for the comments Andrew. I've updated using the getHistogramReport
functionality. The only concern I have is that the values won't exactly match
the "Overall Status" due to some casting to long from doubles. Here is a
snippet of the output. Let me know what you think :) hoping this is a step in
the right direction
{code:java}
2018-09-13 14:30:52,732 INFO
[MultiThreadedAction-ProgressReporter-1536874207705] util.MultiThreadedAction:
[W:20] Keys=82495, cols=927.8 K, time=00:00:45 Overall: [keys/s= 1832,
latency=10.82 ms] Current: [keys/s=2058, latency=9.64 ms], wroteUpTo=-1
2018-09-13 14:30:57,733 INFO
[MultiThreadedAction-ProgressReporter-1536874207705] util.MultiThreadedAction:
[W:20] Keys=92516, cols=1.0 M, time=00:00:50 Overall: [keys/s= 1849,
latency=10.72 ms] Current: [keys/s=2004, latency=9.89 ms], wroteUpTo=-1
2018-09-13 14:31:02,738 INFO
[MultiThreadedAction-ProgressReporter-1536874207705] util.MultiThreadedAction:
RUN SUMMARY
KEYS PER SECOND:
mean=1849.90, min=1108.00, max=2065.00, stdDev=291.71, 50th=1945.50,
75th=2017.50, 95th=2065.00, 99th=2065.00, 99.9th=2065.00, 99.99th=2065.00,
99.999th=2065.00
LATENCY:
mean=10.60, min=9.00, max=17.00, stdDev=2.41, 50th=10.00, 75th=10.50,
95th=17.00, 99th=17.00, 99.9th=17.00, 99.99th=17.00, 99.999th=17.00
{code}
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Colin Garcia
>Priority: Major
> Labels: beginner
> Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch,
> HBASE-20306.002.patch
>
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613962#comment-16613962 ] Andrew Purtell commented on HBASE-20306: I don't think the changes are quite what was asked for. The request is for post run summary statistics, like the summary reports produced by PerformanceEvaluation via getHistogramReport, for example. The patch here changes the running status logging as well via use of the refactored getOverallRunInformation(), which is not what we want, I think. Just add a detailed statistics dump after the run is complete. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16612569#comment-16612569 ] Colin Garcia commented on HBASE-20306: -- [~mdrob] I was wondering if you've had a chance to look this over? > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594341#comment-16594341
]
Hadoop QA commented on HBASE-20306:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
43s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
57s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
17s{color} | {color:red} hbase-server: The patch generated 1 new + 8 unchanged
- 0 fixed = 9 total (was 8) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
37s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
8m 40s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}115m 41s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}155m 44s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.assignment.TestCloseRegionWhileRSCrash |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-20306 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12937332/HBASE-20306.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 67d830b41771 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27
10:45:36 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 5089256529 |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HBASE-Build/14228/artifact/patchprocess/diff-checkstyle-hbase-server.txt
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/14228/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594254#comment-16594254 ] Mike Drob commented on HBASE-20306: --- looks good overall from a quick skim, I'll take a closer look later this week! > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594244#comment-16594244
]
Colin Garcia commented on HBASE-20306:
--
{code:java}
2018-08-27 14:29:33,296 INFO
[MultiThreadedAction-ProgressReporter-1535405323258] util.MultiThreadedAction:
[W:20] Keys=87549, cols=985.4 K, time=00:00:50 Overall: [keys/s= 1749,
latency=11.34 ms] Current: [keys/s=1732, latency=11.47 ms], wroteUpTo=-1
2018-08-27 14:29:38,299 INFO
[MultiThreadedAction-ProgressReporter-1535405323258] util.MultiThreadedAction:
[W:20] Keys=96588, cols=1.1 M, time=00:00:55 Overall: [keys/s= 1754,
latency=11.31 ms] Current: [keys/s=1807, latency=10.98 ms], wroteUpTo=-1
2018-08-27 14:29:43,303 INFO
[MultiThreadedAction-ProgressReporter-1535405323258] util.MultiThreadedAction:
RUN SUMMARY: W Keys=96588, cols=1.1 M, time=00:00:55 Overall: [keys/s= 1754,
latency=11.31 ms] 2018-08-27 14:29:43,324 INFO
[ReadOnlyZKClient-localhost:2181@0x0b6b1987-EventThread] zookeeper.ClientCnxn:
EventThread shut down for session: 0x1657d2d21d30023
{code}
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Colin Garcia
>Priority: Major
> Labels: beginner
> Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch
>
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594241#comment-16594241 ] Colin Garcia commented on HBASE-20306: -- Added your suggestions! > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Colin Garcia >Priority: Major > Labels: beginner > Attachments: HBASE-20306.000.patch, HBASE-20306.001.patch > > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591918#comment-16591918
]
Hadoop QA commented on HBASE-20306:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
19s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
7m 44s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}123m 36s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}159m 31s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.assignment.TestMergeTableRegionsProcedure |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-20306 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12936894/HBASE-20306.000.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 125afa6caca2 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27
10:45:36 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / a452487a9b |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/14190/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/14190/testReport/ |
| Max. process+thread count | 4725 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
|
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591742#comment-16591742
]
Mike Drob commented on HBASE-20306:
---
{code}
+ protected boolean isProgressReporterRunning = false;
{code}
This might need to be volatile (or AtomicBoolean) since it is read from
multiple threads? What happens if an exception is thrown from the {{run()}}
body - then the {{waitForFinish()}} will never finish, right? Overall, we end
up checking the {{numThreadsWorking.get() != 0)}} condition in two places now,
when it's guaranteed to be true by the time isProgressReporterRunning changes
values.
{code}
+ LOG.info("RUN SUMMARY: "
+ + "Keys="
+ + priorNumKeys
+ + ", cols="
+ + StringUtils.humanReadableInt(numCols.get())
+ + ", time="
+ + formatTime(time)
+ + ((priorNumKeys > 0 && time > 0) ? (" Overall: [" + "keys/s= "
+ + priorNumKeys * 1000 / time + ", latency="
+ + String.format("%.2f", (double)priorCumulativeOpTime /
(double)priorNumKeys)
+ + " ms]") : "")
+ );
{code}
Can we pull the parts of this that are common to the in-progress reporting out
into a helper method?
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Colin Garcia
>Priority: Major
> Labels: beginner
> Attachments: HBASE-20306.000.patch
>
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590806#comment-16590806 ] Colin Garcia commented on HBASE-20306: -- No, I just added the logic locally > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590807#comment-16590807 ] Colin Garcia commented on HBASE-20306: -- I'll upload the diff > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590800#comment-16590800
]
Mike Drob commented on HBASE-20306:
---
Is the {{RUN SUMMARY}} line new? I feel like I hadn't seen that before.
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Wei-Chiu Chuang
>Priority: Major
> Labels: beginner
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590796#comment-16590796
]
Colin Garcia commented on HBASE-20306:
--
[~mdrob] I've been looking at this. Based on the output below, do you just want
a final line that's something like the output below? Should I remove the
Overall at each step and just put in overall at the end? Thanks in advance :)
{code:java}
2018-08-23 13:52:52,435 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=45976, cols=972.4 K, time=00:00:30 Overall: [keys/s= 1531,
latency=644.90 ms] Current: [keys/s=2017, latency=492.38 ms], verified=4704
2018-08-23 13:52:57,439 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=56588, cols=1.2 M, time=00:00:35 Overall: [keys/s= 1615,
latency=610.22 ms] Current: [keys/s=2122, latency=459.96 ms], verified=5755
2018-08-23 13:53:02,440 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=63442, cols=1.3 M, time=00:00:40 Overall: [keys/s= 1584,
latency=620.65 ms] Current: [keys/s=1370, latency=706.78 ms], verified=6454
2018-08-23 13:53:07,442 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=72112, cols=1.5 M, time=00:00:45 Overall: [keys/s= 1601,
latency=618.87 ms] Current: [keys/s=1734, latency=605.84 ms], verified=7293
2018-08-23 13:53:12,443 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=82197, cols=1.7 M, time=00:00:50 Overall: [keys/s= 1642,
latency=598.89 ms] Current: [keys/s=2017, latency=455.99 ms], verified=8272
2018-08-23 13:53:17,444 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
[R:1000] Keys=94334, cols=1.9 M, time=00:00:55 Overall: [keys/s= 1714,
latency=580.54 ms] Current: [keys/s=2427, latency=456.27 ms], verified=9511
2018-08-23 13:53:22,445 INFO
[MultiThreadedAction-ProgressReporter-1535057542406] util.MultiThreadedAction:
RUN SUMMARY: Keys=94334, cols=2.1 M, time=00:00:55 Overall: [keys/s= 1714,
latency=580.54 ms]
{code}
> LoadTestTool does not print summary at end of run
> -
>
> Key: HBASE-20306
> URL: https://issues.apache.org/jira/browse/HBASE-20306
> Project: HBase
> Issue Type: Bug
> Components: tooling
>Reporter: Mike Drob
>Assignee: Wei-Chiu Chuang
>Priority: Major
> Labels: beginner
>
> ltt currently prints status as it goes, but doesn't give a nice summary of
> what happened so users have to infer it from the last status line printed.
> Would be nice to print a real summary with statistics about what was run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587823#comment-16587823 ] Colin Garcia commented on HBASE-20306: -- [~jojochuang] I was wondering what progress you've made? Looking to take a look into this as well :) > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522701#comment-16522701 ] Andrew Purtell commented on HBASE-20306: Any progress here? > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418309#comment-16418309 ] Chia-Ping Tsai commented on HBASE-20306: [~jojochuang] I have added you to the contributor group. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20306) LoadTestTool does not print summary at end of run
[ https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418274#comment-16418274 ] Wei-Chiu Chuang commented on HBASE-20306: - Hi Mike, I'd like to take a stab at it. > LoadTestTool does not print summary at end of run > - > > Key: HBASE-20306 > URL: https://issues.apache.org/jira/browse/HBASE-20306 > Project: HBase > Issue Type: Bug > Components: tooling >Reporter: Mike Drob >Priority: Major > Labels: beginner > > ltt currently prints status as it goes, but doesn't give a nice summary of > what happened so users have to infer it from the last status line printed. > Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
