[YARN-3575] Job using 2.5 jars fails on a 2.6 cluster whose RM has been restarted

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.6.0
• Component/s: client
• Target Version/s: 2.7.2
• Assignee: Unassigned
• Reporter: Jason Darrell Lowe
• Created: 04/May/15 21:42
• Updated: 27/Nov/15 17:50
• Resolved: 03/Nov/15 23:38

Description

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.