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

allow capacity scheduler configs maximum-applications and maximum-am-resource-percent configurable on a per queue basis

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.23.0
    • 0.23.3, 2.0.2-alpha
    • mrv2
    • None

    Description

      The capacity scheduler configs for maximum-applications and maximum-am-resource-percent are currently configured globally and then made proportional to each queue based on its capacity. There are times when this may not work well. some exampless - if you have a queue that is running on uberAM jobs, the jobs a queue is running always has a small number of containers, and then you have the opposite where in a queue with very small capacity, you may want to limit the am resources even more so you don't end up deadlocked with all your capacity being used for app masters.

      I think we should make those configurable on a per queue basis.

      Attachments

        1. MAPREDUCE-3893.patch
          15 kB
          Thomas Graves
        2. MAPREDUCE-3893-1.txt
          9 kB
          Eric Payne

        Activity

          People

            tgraves Thomas Graves
            tgraves Thomas Graves
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: