Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.1.0-beta
    • resourcemanager
    • None
    • Reviewed

    Description

      Its possible that after RM shutdown, before AM goes down,AM still call startContainer on NM with containers allocated by previous RM. When RM comes back, NM doesn't know whether this container launch request comes from previous RM or the current RM. we should reject containers allocated by previous RM

      Attachments

        1. YARN-562.1.patch
          26 kB
          Jian He
        2. YARN-562.2.patch
          24 kB
          Jian He
        3. YARN-562.3.patch
          35 kB
          Jian He
        4. YARN-562.4.patch
          59 kB
          Jian He
        5. YARN-562.5.patch
          56 kB
          Jian He
        6. YARN-562.6.patch
          57 kB
          Jian He
        7. YARN-562.7.patch
          54 kB
          Jian He
        8. YARN-562.8.patch
          68 kB
          Jian He
        9. YARN-562.9.patch
          70 kB
          Jian He
        10. YARN-562.10.patch
          76 kB
          Jian He
        11. YARN-562.11.patch
          78 kB
          Jian He
        12. YARN-562.12.patch
          79 kB
          Jian He
        13. YARN-562.12.branch2.patch
          78 kB
          Jian He

        Issue Links

          Activity

            People

              jianhe Jian He
              jianhe Jian He
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: