[HIVE-14215] Displaying inconsistent CPU usage data with MR execution engine

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.1.1, 2.2.0
• Target Version/s: 2.1.1
• Assignee: Peter Vary
• Reporter: Peter Vary
• Created: 12/Jul/16 11:47
• Updated: 08/Dec/16 14:26
• Resolved: 14/Jul/16 16:28

Description

If the MR task is finished after printing the cumulative CPU time then there is the possibility to print inconsistent CPU usage information.

Correct one:

2016-07-12 11:31:42,961 Stage-3 map = 0%,  reduce = 0%
2016-07-12 11:31:48,237 Stage-3 map = 100%,  reduce = 0%, Cumulative CPU 2.5 sec
MapReduce Total cumulative CPU time: 2 seconds 500 msec
Ended Job = job_1468321038188_0003
MapReduce Jobs Launched: 
Stage-Stage-3: Map: 1   Cumulative CPU: 2.5 sec   HDFS Read: 5864 HDFS Write: 103 SUCCESS
Total MapReduce CPU Time Spent: 2 seconds 500 msec

One type of inconsistent data (easily reproducible one):

2016-07-12 11:39:00,540 Stage-3 map = 0%,  reduce = 0%
Ended Job = job_1468321038188_0004
MapReduce Jobs Launched: 
Stage-Stage-3: Map: 1   Cumulative CPU: 2.51 sec   HDFS Read: 5864 HDFS Write: 103 SUCCESS
Total MapReduce CPU Time Spent: 2 seconds 510 msec

Issue Links

• links to: Review