hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4152) map task left hanging after AM dies trying to connect to RM
Date Wed, 23 May 2012 19:09:41 GMT

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

Robert Joseph Evans commented on MAPREDUCE-4152:

I like the patch it looks good to me.  I can agree with you Tom that there should be no issues
with calling kill multiple times, because the protocol does not even provide a way for the
NM to inform the AM that the kill failed.  That being said I do think it would be cleaner
to have the kill method check for the DONE state, and do nothing if it is in the DONE state.

I also agree that once RM restart is in place and it can pick up where it left off we don't
need this any more.  But I have not seem much work going into RM restart lately, and I suspect
that we will be in production before that happens. So I would like to see this go in.

I am +1 on the patch even without the DONE state check in the Container Launcher.
> map task left hanging after AM dies trying to connect to RM
> -----------------------------------------------------------
>                 Key: MAPREDUCE-4152
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4152
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.2
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>         Attachments: MAPREDUCE-4152.patch, MAPREDUCE-4152.patch
> We had an instance where the RM went down for more then an hour.  The application master
exited with "Could not contact RM after 360000 milliseconds"
> 2012-04-11 10:43:36,040 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl:
job_1333003059741_15999Job Transitioned from RUNNING to ERROR

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