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

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/29 22:50:41 UTC

[jira] [Resolved] (MAPREDUCE-1240) refreshQueues does not work correctly when dealing with maximum-capacity

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

Allen Wittenauer resolved MAPREDUCE-1240.
-----------------------------------------

    Resolution: Fixed

Likely stale.

> refreshQueues does not work correctly when dealing with maximum-capacity
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1240
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1240
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Karam Singh
>
> If we comment out or remove maximum-capacity property or set maximum-capacity=-1 for a queue which has maximum-capacity some value (say 60). After using command -:
> mapred mradmin -refreshQueues 
> When we check the Queue Scheduling from Web UI or from CLI it still retains old value and schedules tasks according up to old maximum-capacity if there no other job in cluster where the expected behavior maximum-capacity not retained



--
This message was sent by Atlassian JIRA
(v6.2#6252)