Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-7069 [Umbrella] YARN Resource Profiles phase#2 enhancements
  3. YARN-7541

Node updates don't update the maximum cluster capability for resources other than CPU and memory

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 3.0.0-beta1, 3.1.0
    • 3.0.0, 3.1.0, 2.10.1
    • resourcemanager
    • None
    • Reviewed

    Description

      When I submit an MR job that asks for too much memory or CPU for the map or reduce, the AM will fail because it recognizes that the request is too large. With any other resources, however, the resource requests will instead be made and remain pending forever. Looks like we forgot to update the code that tracks the maximum container allocation in ClusterNodeTracker.

      Attachments

        1. YARN-7541.branch-3.0.001.patch
          17 kB
          Daniel Templeton
        2. YARN-7541.006.patch
          17 kB
          Daniel Templeton
        3. YARN-7541.005.patch
          17 kB
          Daniel Templeton
        4. YARN-7541.004.patch
          17 kB
          Daniel Templeton
        5. YARN-7541.003.patch
          5 kB
          Daniel Templeton
        6. YARN-7541.002.patch
          5 kB
          Daniel Templeton
        7. YARN-7541.001.patch
          5 kB
          Daniel Templeton

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            templedf Daniel Templeton
            templedf Daniel Templeton
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment