[ 
https://issues.apache.org/jira/browse/HADOOP-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716284#action_12716284
 ] 

Hemanth Yamijala commented on HADOOP-5884:
------------------------------------------

Results of test-patch:

     [exec] +1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     +1 tests included.  The patch appears to include 4 new or 
modified tests.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
     [exec]

All capacity scheduler tests pass, except TestQueueCapacities which is being 
tracked elsewhere.

> Capacity scheduler should account high memory jobs as using more capacity of 
> the queue
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5884
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5884
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>            Reporter: Hemanth Yamijala
>            Assignee: Vinod K V
>         Attachments: HADOOP-5884-20090529.1.txt, HADOOP-5884-20090602.1.txt, 
> HADOOP-5884-20090603.txt, HADOOP-5884.patch
>
>
> Currently, when a high memory job is scheduled by the capacity scheduler, 
> each task scheduled counts only once in the capacity of the queue, though it 
> may actually be preventing other jobs from using spare slots on that node 
> because of its higher memory requirements. In order to be fair, the capacity 
> scheduler should proportionally (with respect to default memory) account high 
> memory jobs as using a larger capacity of the queue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to