hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3575) Job using 2.5 jars fails on a 2.6 cluster whose RM has been restarted
Date Mon, 04 May 2015 21:44:07 GMT

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

Jason Lowe commented on YARN-3575:
----------------------------------

Sample error log from a MapReduce AM usign the 2.5 jars:
{noformat}
2015-05-04 21:29:09,852 FATAL [main] org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Error
starting MRAppMaster
java.lang.IllegalArgumentException: Invalid ContainerId: container_e10_1430340923112_5551_01_000001
	at org.apache.hadoop.yarn.api.records.ContainerId.fromString(ContainerId.java:189)
	at org.apache.hadoop.yarn.util.ConverterUtils.toContainerId(ConverterUtils.java:171)
	at org.apache.hadoop.mapreduce.v2.app.MRAppMaster.main(MRAppMaster.java:1400)
Caused by: java.lang.NumberFormatException: For input string: "e10"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Long.parseLong(Long.java:441)
	at java.lang.Long.parseLong(Long.java:483)
	at org.apache.hadoop.yarn.api.records.ContainerId.toApplicationAttemptId(ContainerId.java:196)
	at org.apache.hadoop.yarn.api.records.ContainerId.fromString(ContainerId.java:179)
	... 2 more
2015-05-04 21:29:09,870 INFO [main] org.apache.hadoop.util.ExitUtil: Exiting with status 1
{noformat}

> Job using 2.5 jars fails on a 2.6 cluster whose RM has been restarted
> ---------------------------------------------------------------------
>
>                 Key: YARN-3575
>                 URL: https://issues.apache.org/jira/browse/YARN-3575
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>
> Trying to launch a job that uses the 2.5 jars fails on a 2.6 cluster whose RM has been
restarted (i.e.: epoch != 0) becaue the epoch number starts appearing in the container IDs
and the 2.5 jars no longer know how to parse the container IDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message