Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-1011 [Umbrella] Schedule containers based on utilization of currently allocated containers
  3. YARN-9110

Fair Scheduler promotion does not update container execution type when the application is killed

Add voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: YARN-1011
    • Fix Version/s: None
    • Component/s: fairscheduler
    • Labels:
      None

      Description

      When the application that a container belongs to gets killed right before the container is promoted, the resource booking keeping is updated to reflect the promotion, or, but the container token won't be updated.Hence when the container is released, it is seen as an OPPORTUNISTIC container. 

      We need to make the container promotion, including resource bookkeeping and token update atomic to avoid this problem

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              haibochen Haibo Chen

              Dates

              • Created:
                Updated:

                Issue deployment