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

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

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0-beta, 2.0.5-alpha, 3.0.0-alpha1
    • Fix Version/s: 2.1.0-beta, 0.23.11
    • Component/s: capacityscheduler
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      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

            People

            • Assignee:
              devaraj Devaraj Kavali
              Reporter:
              devaraj Devaraj Kavali
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: