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

Add peak memory usage counter for each task

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0-alpha4, 3.0.0
    • Component/s: mrv2
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      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.

      This JIRA has the same feature from MAPREDUCE-4710. I file this new YARN JIRA since MAPREDUCE-4710 is pretty old one from MR 1.x era, it more or less assumes a branch-1 architecture, should be close at this point.

        Attachments

        1. MAPREDUCE-6829.000.patch
          7 kB
          Miklos Szegedi
        2. MAPREDUCE-6829.001.patch
          14 kB
          Miklos Szegedi
        3. MAPREDUCE-6829.002.patch
          14 kB
          Miklos Szegedi
        4. MAPREDUCE-6829.003.patch
          14 kB
          Miklos Szegedi
        5. MAPREDUCE-6829.004.patch
          14 kB
          Miklos Szegedi
        6. MAPREDUCE-6829.005.patch
          14 kB
          Miklos Szegedi

          Issue Links

            Activity

              People

              • Assignee:
                miklos.szegedi@cloudera.com Miklos Szegedi
                Reporter:
                yufeigu Yufei Gu
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: