[
https://issues.apache.org/jira/browse/YARN-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-3575.
-------------------------------------------
Resolution: Won't Fix
Agreed. I requested that this be filed largely for documentation concerns.
There is one simple way sites can avoid this _incompatibility_: Do not use
RM-recovery on a 2.6+ cluster while you still have applications running
versions < 2.6. Once all apps are upgraded to 2.6+, you can enable RM-recovery
and perform work-preserving RM restarts and rolling upgrades.
Closing this for now as won't fix. Please reopen if you disagree. Thanks.
> 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)
