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

Rajesh Balamohan edited comment on HIVE-16436 at 4/13/17 9:28 AM:
------------------------------------------------------------------

{{perfLogger.PerfLogEnd}} was getting invoked for every report causing this 
issue.

\cc [~anishek], [~gopalv]


was (Author: rajesh.balamohan):
{{perfLogger.PerfLogEnd}} was getting invoked for every report causing this 
issue.

> Response times in "Task Execution Summary" at the end of the job is not 
> correct
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-16436
>                 URL: https://issues.apache.org/jira/browse/HIVE-16436
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: HIVE-16436.1.patch
>
>
> "Task execution summary" is printed at the of running a hive query. E.g
> {noformat}
> Task Execution Summary
> ----------------------------------------------------------------------------------------------
>   VERTICES      DURATION(ms)   CPU_TIME(ms)    GC_TIME(ms)   INPUT_RECORDS   
> OUTPUT_RECORDS
> ----------------------------------------------------------------------------------------------
>      Map 1         277869.00              0              0   1,500,000,000    
> 1,500,000,000
>      Map 2         277868.00              0              0   5,999,989,709    
>    31,162,299
>  Reducer 3          59875.00              0              0   1,531,162,299    
>         2,018
>  Reducer 4           2436.00              0              0           2,018    
>             2
>  Reducer 5            375.00              0              0               2    
>             0
> ----------------------------------------------------------------------------------------------
> {noformat}
> Response times reported here for Map-1/Map-2 is not correct.  Not sure if 
> this is broken due to any other patch. Creating this jira for tracking 
> purpose.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to