[
https://issues.apache.org/jira/browse/MAPREDUCE-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142502#comment-13142502
]
Konstantin Shvachko commented on MAPREDUCE-3286:
------------------------------------------------
This is an example. They are hanging out there since September 15
{code}
jenkins 32743 0.0 0.8 1803048 144544 ? Sl Oct20 3:38
/home/jenkins/tools/java/latest/bin/java -Dlog4j.config
uration=container-log4j.properties
-Dyarn.app.mapreduce.container.log.dir=/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/org.apache.hadoop.mapreduce.v2.TestMRJobs/org.apache.hadoop.mapreduce.v2.TestMRJobs-logDir/application_1319147575527_0003/container_1319147575527_0003_01_000001
-Dyarn.app.mapreduce.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
-Xmx1536m org.apache.hadoop.mapreduce.v2.app.MRAppMaster
{code}
I'll be killing them manually now.
> Unit tests for MAPREDUCE-3186 - User jobs are getting hanged if the Resource
> manager process goes down and comes up while job is getting executed.
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3286
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3286
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: mrv2
> Affects Versions: 0.23.0
> Environment: linux
> Reporter: Eric Payne
> 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