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 "Sharad Agarwal (JIRA)" <ji...@apache.org> on 2011/07/06 07:42:17 UTC

[jira] [Commented] (MAPREDUCE-2646) MR-279: AM with same sized maps and reduces hangs in presence of failing maps

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

Sharad Agarwal commented on MAPREDUCE-2646:
-------------------------------------------

Vinod and I discussed this. It seems like in the returned container list from RM, priority at which the respective
container got allocated is needed. Without which AM cant update the ask/release data structures correctly leading to
resource table in AM and RM going out of sync.

> MR-279: AM with same sized maps and reduces hangs in presence of failing maps
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2646
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2646
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>
> Currently AM can assign a container given by RM to any map or reduce. However RM allocates for a particular priority. This leads to AM and RM data structures going out of sync.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira