Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-270 RM scheduler event handler thread gets behind
  3. YARN-433

When RM is catching up with node updates then it should not expire acquired containers

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: resourcemanager
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      RM expires containers that are not launched within some time of being allocated. The default is 10mins. When an RM is not keeping up with node updates then it may not be aware of new launched containers. If the expire thread fires for such containers then the RM can expire them even though they may have launched.

        Attachments

        1. YARN-433.1.patch
          11 kB
          Xuan Gong
        2. YARN-433.2.patch
          12 kB
          Xuan Gong
        3. YARN-433.3.patch
          11 kB
          Xuan Gong
        4. YARN-433.4.patch
          12 kB
          Xuan Gong

          Activity

            People

            • Assignee:
              xgong Xuan Gong
              Reporter:
              bikassaha Bikas Saha
            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: