hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4073) CS assigns multiple off-switch containers when using multi-level-queues
Date Thu, 29 Mar 2012 16:54:26 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241384#comment-13241384

Siddharth Seth commented on MAPREDUCE-4073:

Arun, the initial patch wasn't dropping the assignment. It was just setting the type - based
on the first allocation. I didn't want to add setters to CSAssignement, since it's a read-only
interface rightnow.
ParentQueue.assignContainer seems to attempt multiple assignments only at the root level -
in which case the return type could be incorrect, but then it's never used outside of ParentQueue
(root) itself.
> CS assigns multiple off-switch containers when using multi-level-queues
> -----------------------------------------------------------------------
>                 Key: MAPREDUCE-4073
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4073
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, scheduler
>    Affects Versions: 0.23.1
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Critical
>         Attachments: MAPREDUCE-4073.patch, MR4073.txt
> CS is supposed to be allocating a single off-switch container per node heartbeat (MAPREDUCE-3641).
This works for queues directly under root, but not in the case of multi-level queues.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message