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

AM does not tell the RM about container requests that are no longer needed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.23.3, 2.0.0-alpha
    • Fix Version/s: 0.23.7, 2.1.0-beta
    • Component/s: None
    • Labels:
      None

      Description

      Say the AM wanted a container at hosts h1, h2, h3. After getting a container at h1 it should tell RM that it no longer needs containers at h2, h3. Otherwise on the RM h2, h3 remain valid allocation locations.
      The AM RMContainerAllocator does remove these resource requests internally. When the resource request container count drops to 0 then it drops the resource request from its tables but forgets to send the 0 sized request to the RM.

        Attachments

        1. MAPREDUCE-4671.1.patch
          4 kB
          Bikas Saha
        2. MAPREDUCE-4671.2.patch
          5 kB
          Bikas Saha
        3. MAPREDUCE-4671.3.patch
          7 kB
          Bikas Saha
        4. MAPREDUCE-4671.4.patch
          7 kB
          Bikas Saha
        5. MAPREDUCE-4671.txt
          7 kB
          Siddharth Seth

          Issue Links

            Activity

              People

              • Assignee:
                bikassaha Bikas Saha
                Reporter:
                bikassaha Bikas Saha
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: