hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4832) MR AM can get in a split brain situation
Date Fri, 30 Nov 2012 11:49:59 GMT

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

Sharad Agarwal commented on MAPREDUCE-4832:
-------------------------------------------

MAPREDUCE-2702 introduced a job level commit. Task commit from competing AMs should not overstep
each other.

Job level commit should ensure only the first one succeeds. Are you observing this in the
cluster ?
                
> MR AM can get in a split brain situation
> ----------------------------------------
>
>                 Key: MAPREDUCE-4832
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4832
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>    Affects Versions: 2.0.2-alpha, 0.23.5
>            Reporter: Robert Joseph Evans
>            Priority: Critical
>
> It is possible for a networking issue to happen where the RM thinks an AM has gone down
and launches a replacement, but the previous AM is still up and running.  If the previous
AM does not need any more resources from the RM it could try to commit either tasks or jobs.
 This could cause lots of problems where the second AM finishes and tries to commit too. 
This could result in data corruption.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message