Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-853

maximum-am-resource-percent doesn't work after refreshQueues command

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1.0-beta, 2.0.5-alpha, 3.0.0-alpha1
    • 2.1.0-beta, 0.23.11
    • capacityscheduler
    • None
    • Reviewed

    Description

      If we update yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent configuration and then do the refreshNodes, it uses the new config value to calculate Max Active Applications and Max Active Application Per User. If we add new node after issuing 'rmadmin -refreshQueues' command, it uses the old maximum-am-resource-percent config value to calculate Max Active Applications and Max Active Application Per User.

      Attachments

        1. YARN-853.patch
          6 kB
          Devaraj Kavali
        2. YARN-853-1.patch
          7 kB
          Devaraj Kavali
        3. YARN-853-2.patch
          7 kB
          Devaraj Kavali
        4. YARN-853-3.patch
          7 kB
          Devaraj Kavali
        5. YARN-853-4.patch
          8 kB
          Vinod Kumar Vavilapalli

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

          People

            devaraj Devaraj Kavali
            devaraj Devaraj Kavali
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment