[ https://issues.apache.org/jira/browse/MAPREDUCE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134518#comment-13134518
]
Eric Payne commented on MAPREDUCE-3186:
---------------------------------------
MRAppMaster still doesn't exit even after adding the check of the reboot flag and returning
from the thread within RMCommunicator.startAllocatorThread().
In the logs, I do see it catching the exception and returning, but it looks like something
is still running.
If I read it correctly, JobHistoryEventHandler is still running as well as ContainerLauncherRouter
and ContainerAllocatorRouter.
Does something need to be done to trigger the CompositeServiceShutdownHook?
> User jobs are getting hanged if the Resource manager process goes down and comes up while
job is getting executed.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3186
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3186
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Environment: linux
> Reporter: Ramgopal N
> Assignee: Eric Payne
> Labels: test
>
> If the resource manager is restarted while the job execution is in progress, the job
is getting hanged.
> UI shows the job as running.
> In the RM log, it is throwing an error "ERROR org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService:
AppAttemptId doesnt exist in cache appattempt_1318579738195_0004_000001"
> In the console MRAppMaster and Runjar processes are not getting killed
--
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
|