You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2008/09/19 08:20:44 UTC

[jira] Updated: (HADOOP-4211) Capacity Scheduler does not divide queue resources properly among users, when jobs are submitted one after other.

     [ https://issues.apache.org/jira/browse/HADOOP-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala updated HADOOP-4211:
-------------------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 0.19.0
         Assignee: Hemanth Yamijala

> Capacity Scheduler does not divide queue resources properly among users, when jobs are submitted one after other.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4211
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4211
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.19.0
>         Environment: Mapred Cluster capacity with 204 Maps and 204 Reduces. User limit =25% and only one queue.
>            Reporter: Karam Singh
>            Assignee: Hemanth Yamijala
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> Capacity Scheduler does not divide queue resources  properly among users, when job are submitted one after other. E.g. user limit =25. Say User1's job is running. Then user2 submits a job. Then user1's job uses 75% and user2's job 25%=user limit.

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