Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-4710

Add peak memory usage counter for each task

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 1.0.2
    • Fix Version/s: None
    • Component/s: task
    • Labels:
      None

      Description

      Each task has counters PHYSICAL_MEMORY_BYTES and VIRTUAL_MEMORY_BYTES, which are snapshots of memory usage of that task. They are not sufficient for users to understand peak memory usage by that task, e.g. in order to diagnose task failures, tune job parameters or change application design. This new feature will add two more counters for each task: PHYSICAL_MEMORY_BYTES_MAX and VIRTUAL_MEMORY_BYTES_MAX.

        Attachments

        1. mapreduce4710.patch
          8 kB
          Cindy Li
        2. mapreduce-4710.patch
          6 kB
          Cindy Li
        3. MAPREDUCE-4710-trunk.patch
          6 kB
          Cindy Li
        4. mapreduce-4710-v1.0.2.patch
          9 kB
          Cindy Li
        5. mapreduce4710-v3.patch
          14 kB
          Cindy Li
        6. mapreduce4710-v6.patch
          14 kB
          Cindy Li

          Issue Links

            Activity

              People

              • Assignee:
                cindyli_2012 Cindy Li
                Reporter:
                cindyli_2012 Cindy Li
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: