[jira] [Created] (MAPREDUCE-5444) MRAppMaster throws InvalidStateTransitonException: Invalid event: JOB_AM_REBOOT at SUCCEEDED
Rohith Sharma K S created MAPREDUCE-5444:
Summary: MRAppMaster throws InvalidStateTransitonException:
Invalid event: JOB_AM_REBOOT at SUCCEEDED
Key: MAPREDUCE-5444
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5444
Project: Hadoop Map/Reduce
Issue Type: Sub-task
Components: applicationmaster
Reporter: Rohith Sharma K S
Priority: Minor
{noformat}
2013-08-02 14:55:11,537 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: Calling handler for
JobFinishedEvent
2013-08-02 14:55:11,538 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1375199817609_0049Job
Transitioned from COMMITTING to SUCCEEDED
2013-08-02 14:55:11,663 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copying
hdfs://0.0.0.0:45000/home/restest/staging-dir/restest/.staging/job_1375199817609_0049/job_1375199817609_0049_2.jhist
to
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049-1375435337429-restest-word+count-1375435511533-10-1-SUCCEEDED-a.jhist_tmp
2013-08-02 14:55:11,750 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copied to done
location:
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049-1375435337429-restest-word+count-1375435511533-10-1-SUCCEEDED-a.jhist_tmp
2013-08-02 14:55:11,769 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copying
hdfs://0.0.0.0:45000/home/restest/staging-dir/restest/.staging/job_1375199817609_0049/job_1375199817609_0049_2_conf.xml
to
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049_conf.xml_tmp
2013-08-02 14:55:11,880 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:1
CompletedMaps:10 CompletedReds:1 ContAlloc:1 ContRel:0 HostLocal:0 RackLocal:0
2013-08-02 14:55:13,649 ERROR [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Error communicating
with RM: Resource Manager doesn't recognize AttemptId:
application_1375199817609_0049
org.apache.hadoop.yarn.YarnException: Resource Manager doesn't recognize
AttemptId: application_1375199817609_0049
at
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.getResources(RMContainerAllocator.java:626)
at
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.heartbeat(RMContainerAllocator.java:238)
at
org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator$1.run(RMCommunicator.java:250)
at java.lang.Thread.run(Thread.java:662)
2013-08-02 14:55:13,649 ERROR [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: Can't handle this event at
current state
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
JOB_AM_REBOOT at SUCCEEDED
at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
at
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:43)
at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:445)
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:914)
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:129)
at
org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobEventDispatcher.handle(MRAppMaster.java:1114)
at
org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobEventDispatcher.handle(MRAppMaster.java:1110)
at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:130)
at
org.apache.hadoop.mapreduce.v2.app.recover.RecoveryService$RecoveryDispatcher.realDispatch(RecoveryService.java:309)
at
org.apache.hadoop.mapreduce.v2.app.recover.RecoveryService$RecoveryDispatcher.dispatch(RecoveryService.java:305)
at
org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:77)
at java.lang.Thread.run(Thread.java:662)
2013-08-02 14:55:13,652 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: JobHistoryEvent is
triggered from JobImpl
2013-08-02 14:55:13,652 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1375199817609_0049Job
Transitioned from SUCCEEDED to ERROR
{noformat}
--
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
Hadoop-Mapreduce-trunk - Build # 1506 - Failure
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1506/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 30138 lines...] Running org.apache.hadoop.mapreduce.v2.hs.webapp.TestBlocks Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.144 sec Running org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServices Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.606 sec Running org.apache.hadoop.mapreduce.v2.hs.TestJobHistoryEntities Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.203 sec Running org.apache.hadoop.mapreduce.v2.hs.TestJobListCache Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.472 sec Running org.apache.hadoop.mapreduce.v2.hs.TestJobHistoryParsing Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.924 sec Running org.apache.hadoop.mapreduce.v2.hs.TestJobIdHistoryFileInfoMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.448 sec Results : Tests run: 152, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-mapreduce-client ... SUCCESS [1.861s] [INFO] hadoop-mapreduce-client-core .. SUCCESS [38.185s] [INFO] hadoop-mapreduce-client-common SUCCESS [23.878s] [INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [2.272s] [INFO] hadoop-mapreduce-client-app ... SUCCESS [5:44.484s] [INFO] hadoop-mapreduce-client-hs FAILURE [1:36.002s] [INFO] hadoop-mapreduce-client-jobclient . SKIPPED [INFO] hadoop-mapreduce-client-hs-plugins SKIPPED [INFO] Apache Hadoop MapReduce Examples .. SKIPPED [INFO] hadoop-mapreduce .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 8:27.315s [INFO] Finished at: Fri Aug 02 13:25:15 UTC 2013 [INFO] Final Memory: 21M/225M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on project hadoop-mapreduce-client-hs: ExecutionException; nested exception is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-mapreduce-client-hs Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Archiving artifacts Updating YARN-573 Updating YARN-903 Updating MAPREDUCE-5428 Updating HADOOP-9806 Updating MAPREDUCE-5352 Updating HDFS-5028 Updating HADOOP-9801 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
On 30 July 2013 14:29, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would like to get released. This RC fixes a number of issues reported on the previous candidate. This release represents a *huge* amount of work done by the community (~650 fixes) which includes several major advances including: # HDFS Snapshots # Windows support # YARN API stabilization # MapReduce Binary Compatibility with hadoop-1.x # Substantial amount of integration testing with rest of projects in the ecosystem The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc1/ The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1 The maven artifacts are available via repository.apache.org. +1 set my Hoya Hbase-on-YARN app to build and run against the staging artifacts, and after catching up w/ some minor API changes, all is well -not only to the binaries work, but the POMs set up the downstream classpath with (at least) everything you need I filed one minor JIRA, prereq check for AMRMClient.ContainerRequest relaxLocality flag wrong: https://issues.apache.org/jira/browse/YARN-1018 -Steve
[jira] [Resolved] (MAPREDUCE-5444) MRAppMaster throws InvalidStateTransitonException: Invalid event: JOB_AM_REBOOT at SUCCEEDED
[
https://issues.apache.org/jira/browse/MAPREDUCE-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved MAPREDUCE-5444.
---
Resolution: Invalid
bq. I have one point to add here that, immidiately after job is succeeded , app
master got reboot command from RM. JobClient is exitted( see MAPREDUCE-5441 ).
By the time, RM has launched 2nd attempt of app master. 2nd attempt app master
too compete for resources, but there is no client waiting getting job report.I
feel this is problem.
There will always be a race where the job has just succeeded but the RM gets
out of sync with the AM before the AM can unregister. Normally the AM will
exit, another AM attempt will be launched by the RM, and the new attempt will
recover the previous SUCCEEDED state and exit shortly afterwards without
launching any subsequent tasks.
As for the client, that's an orthogonal problem. It's not required that a
client be listening to an application as it executes, and if the client is
unnecessarily exiting across an AM restart then we can tackle that issue in
MAPREDUCE-5441.
MRAppMaster throws InvalidStateTransitonException: Invalid event:
JOB_AM_REBOOT at SUCCEEDED
Key: MAPREDUCE-5444
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5444
Project: Hadoop Map/Reduce
Issue Type: Sub-task
Components: applicationmaster
Reporter: Rohith Sharma K S
Priority: Minor
{noformat}
2013-08-02 14:55:11,537 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: Calling handler for
JobFinishedEvent
2013-08-02 14:55:11,538 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl:
job_1375199817609_0049Job Transitioned from COMMITTING to SUCCEEDED
2013-08-02 14:55:11,663 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copying
hdfs://0.0.0.0:45000/home/restest/staging-dir/restest/.staging/job_1375199817609_0049/job_1375199817609_0049_2.jhist
to
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049-1375435337429-restest-word+count-1375435511533-10-1-SUCCEEDED-a.jhist_tmp
2013-08-02 14:55:11,750 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copied to done
location:
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049-1375435337429-restest-word+count-1375435511533-10-1-SUCCEEDED-a.jhist_tmp
2013-08-02 14:55:11,769 INFO [Thread-52]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler: Copying
hdfs://0.0.0.0:45000/home/restest/staging-dir/restest/.staging/job_1375199817609_0049/job_1375199817609_0049_2_conf.xml
to
hdfs://0.0.0.0:45000/home/restest/staging-dir/history/done_intermediate/restest/job_1375199817609_0049_conf.xml_tmp
2013-08-02 14:55:11,880 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:10 CompletedReds:1 ContAlloc:1 ContRel:0
HostLocal:0 RackLocal:0
2013-08-02 14:55:13,649 ERROR [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Error
communicating with RM: Resource Manager doesn't recognize AttemptId:
application_1375199817609_0049
org.apache.hadoop.yarn.YarnException: Resource Manager doesn't recognize
AttemptId: application_1375199817609_0049
at
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.getResources(RMContainerAllocator.java:626)
at
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.heartbeat(RMContainerAllocator.java:238)
at
org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator$1.run(RMCommunicator.java:250)
at java.lang.Thread.run(Thread.java:662)
2013-08-02 14:55:13,649 ERROR [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: Can't handle this event
at current state
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
JOB_AM_REBOOT at SUCCEEDED
at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
at
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:43)
at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:445)
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:914)
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:129)
at
[jira] [Reopened] (MAPREDUCE-5311) Remove slot millis computation logic and deprecate counter constants
[ https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza reopened MAPREDUCE-5311: --- Remove slot millis computation logic and deprecate counter constants Key: MAPREDUCE-5311 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5311 Project: Hadoop Map/Reduce Issue Type: Bug Components: applicationmaster Affects Versions: 2.0.4-alpha Reporter: Alejandro Abdelnur Assignee: Sandy Ryza Attachments: MAPREDUCE-5311.patch, MAPREDUCE-5311.patch Per discussion in MAPREDUCE-5310 and comments in the code we should remove all the related logic and just leave the counter constant for backwards compatibility and deprecate the counter constants. -- 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
[jira] [Created] (MAPREDUCE-5445) MRApp tries to stop services from AsyncDispatcher thread
Jason Lowe created MAPREDUCE-5445: - Summary: MRApp tries to stop services from AsyncDispatcher thread Key: MAPREDUCE-5445 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5445 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2, test Affects Versions: 2.0.5-alpha Reporter: Jason Lowe MRApp tries to stop services from within a service thread. That causes the stop call itself to be interrupted and not all services are stopped. -- 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
[jira] [Created] (MAPREDUCE-5446) TestJobHistoryEvents and TestJobHistoryParsing have race conditions
Jason Lowe created MAPREDUCE-5446: - Summary: TestJobHistoryEvents and TestJobHistoryParsing have race conditions Key: MAPREDUCE-5446 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5446 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2, test Affects Versions: 2.1.0-beta Reporter: Jason Lowe TestJobHistoryEvents and TestJobHistoryParsing are not properly waiting for MRApp to finish. Currently they are polling the service state looking for Service.STATE.STOPPED, but the service can appear to be in that state *before* it is fully stopped. This causes tests to finish with MRApp threads still in-flight, and those threads can conflict with subsequent tests when they collide in the filesystem. -- 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
