Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4862

Handle duplicate completed containers in RMNodeImpl

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-alpha2
    • Component/s: resourcemanager
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      As per comment from Sharad Agarwal, there should be safe guard for duplicated container status in RMNodeImpl before creating UpdatedContainerInfo.
      Or else in heavily loaded cluster where event processing is gradually slow, if any duplicated container are sent to RM(may be bug in NM also), there is significant impact that RMNodImpl always create UpdatedContainerInfo for duplicated containers. This result in increase in the heap memory and causes problem like YARN-4852.
      This is an optimization for issue kind YARN-4852

        Attachments

        1. 0001-YARN-4862.patch
          6 kB
          Rohith Sharma K S
        2. 0002-YARN-4862.patch
          6 kB
          Rohith Sharma K S
        3. 0003-YARN-4862.patch
          7 kB
          Rohith Sharma K S
        4. YARN-4862-004.patch
          13 kB
          Rohith Sharma K S
        5. YARN-4862-005.patch
          13 kB
          Rohith Sharma K S
        6. YARN-4862-006.patch
          14 kB
          Rohith Sharma K S

          Activity

            People

            • Assignee:
              rohithsharma Rohith Sharma K S
              Reporter:
              rohithsharma Rohith Sharma K S
            • Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: