You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Dick King (JIRA)" <ji...@apache.org> on 2010/08/27 23:05:54 UTC

[jira] Created: (MAPREDUCE-2037) Capturing interim progress times, CPU usage, and memory usage, when tasks reach certain progress thresholds

Capturing interim progress times, CPU usage, and memory usage, when tasks reach certain progress thresholds
-----------------------------------------------------------------------------------------------------------

                 Key: MAPREDUCE-2037
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2037
             Project: Hadoop Map/Reduce
          Issue Type: New Feature
            Reporter: Dick King
            Assignee: Dick King
             Fix For: 0.22.0


We would like to capture the following information at certain progress thresholds as a task runs:

   * Time taken so far
   * CPU load [either at the time the data are taken, or exponentially smoothed]
   * Memory load [also either at the time the data are taken, or exponentially smoothed]

This would be taken at intervals that depend on the task progress plateaus.  For example, reducers have three progress ranges -- [0-1/3], (1/3-2/3], and (2/3-3/3] -- where fundamentally different activities happen.  Mappers have different boundaries, I understand, that are not symmetrically placed.  Data capture boundaries should coincide with activity boundaries.  For the state information capture [CPU and memory] we should average over the covered interval.

This data would flow in with the heartbeats.  It would be placed in the job history as part of the task attempt completion event, so it could be processed by rumen or some similar tool and could drive a benchmark engine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.