[ 
https://issues.apache.org/jira/browse/HBASE-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636264#comment-16636264
 ] 

Colin Garcia edited comment on HBASE-20306 at 10/3/18 12:16 AM:
----------------------------------------------------------------

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. 

I'm rerunning to see if I can mimic the behavior you describe. 


was (Author: colingarcia):
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)

Reply via email to