Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-3328

mapred queue -list output inconsistent and missing child queues

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 0.23.1
    • Component/s: mrv2
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When running mapred queue -list on a 0.23.0 cluster with capacity scheduler configured with child queues. In my case I have queues default, test1, and test2. test1 has subqueues of a1, a2. test2 has subqueues of a3 and a4.

      • the child queues do not show up
      • The output of maximum capacity doesn't match the format of the current capacity and capacity. the latter two use float while the maximum is specified as int:

      Queue Name : default
      Queue State : running
      Scheduling Info : queueName: "default", capacity: 0.7, maximumCapacity: 90.0, currentCapacity: 0.0, state: Q_RUNNING,
      ======================
      Queue Name : test
      Queue State : running
      Scheduling Info : queueName: "test", capacity: 0.2, maximumCapacity: -1.0, currentCapacity: 0.0, state: Q_RUNNING,
      ======================
      Queue Name : test2
      Queue State : running
      Scheduling Info : queueName: "test2", capacity: 0.1, maximumCapacity: 5.0, currentCapacity: 0.0, state: Q_RUNNING,
      ======================

      here default is configured to have capacity=70% and maximum capacity = 90%

      1. MAPREDUCE-3328.branch-0.23.patch
        15 kB
        Ravi Prakash
      2. MAPREDUCE-3328.trunk.patch
        10 kB
        Ravi Prakash
      3. MAPREDUCE-3328.trunk.patch
        13 kB
        Ravi Prakash
      4. MAPREDUCE-3328.trunk.patch
        15 kB
        Ravi Prakash

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Ravi Prakash
            Reporter:
            Thomas Graves
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development