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

Capacity Scheduler scheduling information is hard to read / should be tabular format

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.2
    • Fix Version/s: 0.20.203.0, 0.22.0
    • Component/s: capacity-sched
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Add CapacityScheduler servlet to enhance web UI for queue information.

      Description

      The scheduling information provided by the capacity scheduler is extremely hard to read on the job tracker web page. Instead of just flat text, it should be presenting the information in a tabular format, similar to what the fair share scheduler provides. This makes it much easier to compare what different queues are doing.

      1. MR-1118-22.patch
        30 kB
        Milind Bhandarkar
      2. mapred-1118-3.patch
        30 kB
        Krishna Ramachandran
      3. mapred-1118-2.patch
        30 kB
        Krishna Ramachandran
      4. mapred-1118-1.patch
        29 kB
        Krishna Ramachandran
      5. mapred-1118.20S.patch
        33 kB
        Krishna Ramachandran
      6. mapred-1118.patch
        26 kB
        Krishna Ramachandran

        Activity

        Hide
        Vinod Kumar Vavilapalli added a comment -

        On trunk, the queue information is moved into a new page queueinfo.jsp which is linked to from jobtracker.jsp. One can now look at information for each queue separately, at any time information of only one queue is presented. That should address the readability problem.

        If we want cross queue-comparison, that is a new ask.

        Show
        Vinod Kumar Vavilapalli added a comment - On trunk, the queue information is moved into a new page queueinfo.jsp which is linked to from jobtracker.jsp. One can now look at information for each queue separately, at any time information of only one queue is presented. That should address the readability problem. If we want cross queue-comparison, that is a new ask.
        Hide
        Allen Wittenauer added a comment -

        Flipping between multiple pages to present the same info is even worse. It basically means I'd need a web browser window per queue.

        So yes, make this a new ask then: a decent, readable summary of all queue information such that one could intelligently compare what is happening in each queue in relation to the other queues. See also the Fair Share Scheduler's /scheduler page as an example.

        Show
        Allen Wittenauer added a comment - Flipping between multiple pages to present the same info is even worse. It basically means I'd need a web browser window per queue. So yes, make this a new ask then: a decent, readable summary of all queue information such that one could intelligently compare what is happening in each queue in relation to the other queues. See also the Fair Share Scheduler's /scheduler page as an example.
        Hide
        Hemanth Yamijala added a comment -

        Would the same apply for Command line as well ? mapred queue -info ?

        Show
        Hemanth Yamijala added a comment - Would the same apply for Command line as well ? mapred queue -info ?
        Hide
        Allen Wittenauer added a comment -

        The command line needs machine parse-able output that is scheduler agnostic. But I sort of view that as a separate issue.

        Show
        Allen Wittenauer added a comment - The command line needs machine parse-able output that is scheduler agnostic. But I sort of view that as a separate issue.
        Hide
        Krishna Ramachandran added a comment -

        Added a servlet to tabulate CapacityTaskScheduler queue stats

        Show
        Krishna Ramachandran added a comment - Added a servlet to tabulate CapacityTaskScheduler queue stats
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12447576/mapred-1118.patch
        against trunk revision 956335.

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        -1 findbugs. The patch appears to introduce 3 new Findbugs warnings.

        -1 release audit. The applied patch generated 2 release audit warnings (more than the trunk's current 0 warnings).

        +1 core tests. The patch passed core unit tests.

        -1 contrib tests. The patch failed contrib unit tests.

        Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/testReport/
        Release audit warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/patchprocess/releaseAuditDiffWarnings.txt
        Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/build/test/checkstyle-errors.html
        Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12447576/mapred-1118.patch against trunk revision 956335. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 3 new Findbugs warnings. -1 release audit. The applied patch generated 2 release audit warnings (more than the trunk's current 0 warnings). +1 core tests. The patch passed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/testReport/ Release audit warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/patchprocess/releaseAuditDiffWarnings.txt Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/256/console This message is automatically generated.
        Hide
        Krishna Ramachandran added a comment -

        patch revised

        Show
        Krishna Ramachandran added a comment - patch revised
        Hide
        Krishna Ramachandran added a comment -

        Fix for an earlier release not for commit in trunk

        Show
        Krishna Ramachandran added a comment - Fix for an earlier release not for commit in trunk
        Hide
        Krishna Ramachandran added a comment -

        patch revised

        Show
        Krishna Ramachandran added a comment - patch revised
        Hide
        Krishna Ramachandran added a comment -

        minor revision from previous version

        Show
        Krishna Ramachandran added a comment - minor revision from previous version
        Hide
        Dick King added a comment -

        This comment is a review.

        First, let me say that I didn't review sorttable.js . It would be bad to have subtly different versions of this code flying around.

        CapacitySchedulerServlet.java

        near end of doGet() :

        This is serious: ByteArrayOutputSteam.writeTo(OutputStream) throws. Please revise this call to something like

          OutputStream servletOut = null;
          try {
            servletOut = response.getOutputStream();
            baos.writeTo(servletOut);
          } finally {
            if (servletOut != null) {
              servletOut.close();
            }
          }
        

        .

        This is semi-serious: In showQueues , where queues are printed, the code

          out.printf(
                "<td><a href=\"jobqueue_details.jsp?queueName=%s\">%s</a></td>\n",
                name, name);
        

        the code deposits the name right in the middle of hard-core HTML. If the queue names contain obnoxious characters such as a quote or an angle bracket we could have a bad day. These characters should be escaped with HTML escape sequences such as < , etc.

        Don't forget to escape the ampersands . I believe that only quote marks and angle brackets need to be escaped in the URL, but everything needs to be escaped in the rendered text.

        This is a nit: In

           out.printf("<td>%s</td>\n", queuesManager.getJobQueue(name)
                .getRunningJobs().size());
           out.printf("<td>%s</td>\n", qsc.getNumOfWaitingJobs());
        

        I can't condone dropping numeric data onto a %s . I realize that it works but it looks ugly to my eye.

        This is potentially serious: I don't see where showQueues does the needed locking. You allude to this by defensively dumping into a ByteArrayOutputStream , but the code doesn't lock anything. I can see why it should. Can queues disappear or appear?

        This is a potential omission: The block comment before the class declaration claims to implement an advanced mode, but I don't see any footprint of such a thing in the code. In any event, I'm not a big fan of magic URLs. The servlet should include a button to bring itself into advanced mode. If there are users that shouldn't be able to go into advanced mode, this should be handled in some other manner than hidden URLs.

        I don't see the code to get into the scheduler manager servlet. Perhaps there should be a button in the job tracker administration page when the capacity scheduler is in use?

        TaskSchedulingMgr

        infoServer.setAttribute("scheduler", this);

        This is a nit: I would prefer infoServer.setAttribute("scheduler.scheduler", this); . All of the servlets share an attribute namespace. However, this one isn't bad as such things go, since it's hard to imagine another servlet code author putting anything except the ambient scheduler into that attribute.

        TestCapacitySchedulerServlet

        This is a minor nit.

        I can't condone assertTrue(queueData.contains("50.0%")); . That's the moral equivalent of floating point equality. I do realize that 1/2 can be represented exactly in most float systems, but you might want to do something else, even if only allowing the value to be 49.9 which is okay because the servlet does print it out as a %.1f .

        Show
        Dick King added a comment - This comment is a review. First, let me say that I didn't review sorttable.js . It would be bad to have subtly different versions of this code flying around. CapacitySchedulerServlet.java near end of doGet() : This is serious : ByteArrayOutputSteam.writeTo(OutputStream) throws. Please revise this call to something like OutputStream servletOut = null; try { servletOut = response.getOutputStream(); baos.writeTo(servletOut); } finally { if (servletOut != null) { servletOut.close(); } } . This is semi-serious : In showQueues , where queues are printed, the code out.printf( "<td><a href=\"jobqueue_details.jsp?queueName=%s\">%s</a></td>\n", name, name); the code deposits the name right in the middle of hard-core HTML. If the queue names contain obnoxious characters such as a quote or an angle bracket we could have a bad day. These characters should be escaped with HTML escape sequences such as < , etc. Don't forget to escape the ampersands . I believe that only quote marks and angle brackets need to be escaped in the URL, but everything needs to be escaped in the rendered text. This is a nit : In out.printf("<td>%s</td>\n", queuesManager.getJobQueue(name) .getRunningJobs().size()); out.printf("<td>%s</td>\n", qsc.getNumOfWaitingJobs()); I can't condone dropping numeric data onto a %s . I realize that it works but it looks ugly to my eye. This is potentially serious : I don't see where showQueues does the needed locking. You allude to this by defensively dumping into a ByteArrayOutputStream , but the code doesn't lock anything. I can see why it should. Can queues disappear or appear? This is a potential omission : The block comment before the class declaration claims to implement an advanced mode, but I don't see any footprint of such a thing in the code. In any event, I'm not a big fan of magic URLs. The servlet should include a button to bring itself into advanced mode. If there are users that shouldn't be able to go into advanced mode, this should be handled in some other manner than hidden URLs. I don't see the code to get into the scheduler manager servlet. Perhaps there should be a button in the job tracker administration page when the capacity scheduler is in use? TaskSchedulingMgr infoServer.setAttribute("scheduler", this); This is a nit : I would prefer infoServer.setAttribute("scheduler.scheduler", this); . All of the servlets share an attribute namespace. However, this one isn't bad as such things go, since it's hard to imagine another servlet code author putting anything except the ambient scheduler into that attribute. TestCapacitySchedulerServlet This is a minor nit. I can't condone assertTrue(queueData.contains("50.0%")); . That's the moral equivalent of floating point equality. I do realize that 1/2 can be represented exactly in most float systems, but you might want to do something else, even if only allowing the value to be 49.9 which is okay because the servlet does print it out as a %.1f .
        Hide
        Krishna Ramachandran added a comment -

        Incorporate review recommendations (Dick)
        Have taken care of the "serious ones"

        Show
        Krishna Ramachandran added a comment - Incorporate review recommendations (Dick) Have taken care of the "serious ones"
        Hide
        Hemanth Yamijala added a comment -

        I took this patch for a spin. Without going into too much detail of the code, I could see some high level points to discuss:

        • The /scheduler page that is being added does not have all the fields for the queues - it only has fields related to capacity parameters. The queueinfo page on the other hand has more fields - like tasks, limits, job counts etc . I would imagine we'll need more information in the servlet, no ? Allen ?
        • The patch doesn't play well with hierarchical queues introduced in Hadoop 0.21 (MAPREDUCE-853). When I configured a simple hierarchy: parent level queues: p1 and p2, each having one child queue: q1 and q2 respectively, I got the following exception when I accessed /scheduler:
        java.lang.NullPointerException
        	at org.apache.hadoop.mapred.CapacitySchedulerServlet.showQueues(CapacitySchedulerServlet.java:127)
        	at org.apache.hadoop.mapred.CapacitySchedulerServlet.doGet(CapacitySchedulerServlet.java:90)
        	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        

        More importantly, I am not even sure what should be displayed in the case of hierarchical queues that makes sense to meet Allen's original requirement - i.e. provide an easy-to-read interface to compare queue information. The confusion clearly is that queues across hierarchies do not make sense to be compared (unless the information is normalized at some global level). So, probably what makes sense is to have this kind of tabular structure for queues at every level. Clearly, this issue does not arise for Hadoop 0.20.

        • From an interface point of view, I think we can do better in how scheduling information is accessed from the main page. This information has been available via the 'queues' link, and this patch adds another entry point - the /scheduler page. Perhaps discussion around the hierarchical queue interface will give us ideas around this as well.
        Show
        Hemanth Yamijala added a comment - I took this patch for a spin. Without going into too much detail of the code, I could see some high level points to discuss: The /scheduler page that is being added does not have all the fields for the queues - it only has fields related to capacity parameters. The queueinfo page on the other hand has more fields - like tasks, limits, job counts etc . I would imagine we'll need more information in the servlet, no ? Allen ? The patch doesn't play well with hierarchical queues introduced in Hadoop 0.21 ( MAPREDUCE-853 ). When I configured a simple hierarchy: parent level queues: p1 and p2, each having one child queue: q1 and q2 respectively, I got the following exception when I accessed /scheduler: java.lang.NullPointerException at org.apache.hadoop.mapred.CapacitySchedulerServlet.showQueues(CapacitySchedulerServlet.java:127) at org.apache.hadoop.mapred.CapacitySchedulerServlet.doGet(CapacitySchedulerServlet.java:90) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) More importantly, I am not even sure what should be displayed in the case of hierarchical queues that makes sense to meet Allen's original requirement - i.e. provide an easy-to-read interface to compare queue information. The confusion clearly is that queues across hierarchies do not make sense to be compared (unless the information is normalized at some global level). So, probably what makes sense is to have this kind of tabular structure for queues at every level. Clearly, this issue does not arise for Hadoop 0.20. From an interface point of view, I think we can do better in how scheduling information is accessed from the main page. This information has been available via the 'queues' link, and this patch adds another entry point - the /scheduler page. Perhaps discussion around the hierarchical queue interface will give us ideas around this as well.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12451964/mapred-1118-3.patch
        against trunk revision 1075216.

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 2 new or modified tests.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings.

        -1 release audit. The applied patch generated 4 release audit warnings (more than the trunk's current 2 warnings).

        +1 core tests. The patch passed core unit tests.

        -1 contrib tests. The patch failed contrib unit tests.

        +1 system test framework. The patch passed system test framework compile.

        Test results: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//testReport/
        Release audit warnings: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
        Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12451964/mapred-1118-3.patch against trunk revision 1075216. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. -1 release audit. The applied patch generated 4 release audit warnings (more than the trunk's current 2 warnings). +1 core tests. The patch passed core unit tests. -1 contrib tests. The patch failed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//testReport/ Release audit warnings: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/94//console This message is automatically generated.
        Hide
        Arun C Murthy added a comment -

        Fixed in 0.20.203, no point in fwd-porting with MRv2 in now.

        Show
        Arun C Murthy added a comment - Fixed in 0.20.203, no point in fwd-porting with MRv2 in now.
        Hide
        Konstantin Shvachko added a comment -

        Needs to be ported to 0.22

        Show
        Konstantin Shvachko added a comment - Needs to be ported to 0.22
        Hide
        Milind Bhandarkar added a comment -

        Straightforward port for 0.22.

        Show
        Milind Bhandarkar added a comment - Straightforward port for 0.22.
        Hide
        Milind Bhandarkar added a comment -

        Patch for 0.22.

        Show
        Milind Bhandarkar added a comment - Patch for 0.22.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12502498/MR-1118-22.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 3 new or modified tests.

        -1 patch. The patch command could not apply the patch.

        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1248//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12502498/MR-1118-22.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1248//console This message is automatically generated.
        Hide
        Konstantin Shvachko added a comment -

        Did you forget to include sorttable.js?
        No need to make patch available for .22. Jenkins kick off works only for trunk.

        Show
        Konstantin Shvachko added a comment - Did you forget to include sorttable.js? No need to make patch available for .22. Jenkins kick off works only for trunk.
        Hide
        Milind Bhandarkar added a comment -

        Correct patch for 0.22 (this time with sorttable.js.)

        Show
        Milind Bhandarkar added a comment - Correct patch for 0.22 (this time with sorttable.js.)
        Hide
        Konstantin Shvachko added a comment -

        The test is failing. Run
        ant -Dtestcase=TestCapacitySchedulerServlet -Dtest.output=yes test-contrib
        you will see.

        Show
        Konstantin Shvachko added a comment - The test is failing. Run ant -Dtestcase=TestCapacitySchedulerServlet -Dtest.output=yes test-contrib you will see.
        Hide
        Milind Bhandarkar added a comment -

        Arrgh.. i forgot that contrib and test-contrib are not run when i do ant test. I will take a look. Thanks.

        Show
        Milind Bhandarkar added a comment - Arrgh.. i forgot that contrib and test-contrib are not run when i do ant test. I will take a look. Thanks.
        Hide
        Milind Bhandarkar added a comment -

        Fixed the test. The problem was that, JT fails to start unless

        clusterProps.put(JTConfig.JT_PERSIST_JOBSTATUS, "false");
        

        is set.

        Show
        Milind Bhandarkar added a comment - Fixed the test. The problem was that, JT fails to start unless clusterProps.put(JTConfig.JT_PERSIST_JOBSTATUS, " false " ); is set.
        Hide
        Milind Bhandarkar added a comment -

        Result off:

        ant -Dtestcase=TestCapacitySchedulerServlet -Dtest.output=yes test-contrib -Dresolvers=internal
        

        is:

        
            [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.019 sec
        
        Show
        Milind Bhandarkar added a comment - Result off: ant -Dtestcase=TestCapacitySchedulerServlet -Dtest.output=yes test-contrib -Dresolvers=internal is: [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.019 sec
        Hide
        Konstantin Shvachko added a comment -

        I just committed this to 0.22 branch. Thank you Milind.

        Show
        Konstantin Shvachko added a comment - I just committed this to 0.22 branch. Thank you Milind.
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-22-branch #88 (See https://builds.apache.org/job/Hadoop-Mapreduce-22-branch/88/)
        MAPREDUCE-1118. Enhance the JobTracker web-ui to ensure tabular columns are sortable, also added a /scheduler servlet to CapacityScheduler for enhanced UI for queue information. Contributed by Krishna Ramachandran and Milind Bhandarkar.

        shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1198122
        Files :

        • /hadoop/common/branches/branch-0.22/mapreduce/CHANGES.txt
        • /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/java/org/apache/hadoop/mapred/CapacitySchedulerServlet.java
        • /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/java/org/apache/hadoop/mapred/CapacityTaskScheduler.java
        • /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/test/org/apache/hadoop/mapred/TestCapacitySchedulerServlet.java
        • /hadoop/common/branches/branch-0.22/mapreduce/src/java/org/apache/hadoop/mapred/JSPUtil.java
        • /hadoop/common/branches/branch-0.22/mapreduce/src/webapps/static/sorttable.js
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-22-branch #88 (See https://builds.apache.org/job/Hadoop-Mapreduce-22-branch/88/ ) MAPREDUCE-1118 . Enhance the JobTracker web-ui to ensure tabular columns are sortable, also added a /scheduler servlet to CapacityScheduler for enhanced UI for queue information. Contributed by Krishna Ramachandran and Milind Bhandarkar. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1198122 Files : /hadoop/common/branches/branch-0.22/mapreduce/CHANGES.txt /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/java/org/apache/hadoop/mapred/CapacitySchedulerServlet.java /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/java/org/apache/hadoop/mapred/CapacityTaskScheduler.java /hadoop/common/branches/branch-0.22/mapreduce/src/contrib/capacity-scheduler/src/test/org/apache/hadoop/mapred/TestCapacitySchedulerServlet.java /hadoop/common/branches/branch-0.22/mapreduce/src/java/org/apache/hadoop/mapred/JSPUtil.java /hadoop/common/branches/branch-0.22/mapreduce/src/webapps/static/sorttable.js

          People

          • Assignee:
            Krishna Ramachandran
            Reporter:
            Allen Wittenauer
          • Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development