[MAPREDUCE-2793] [MR-279] Maintain consistency in naming appIDs, jobIDs and attemptIDs

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.0
• Fix Version/s: 0.23.2
• Component/s: mrv2
• Target Version/s: 0.23.2
• Hadoop Flags: Reviewed
• Release Note: Corrected AppIDs, JobIDs, TaskAttemptIDs to be of correct format on the web pages.
• Assignee: Bikas Saha
• Reporter: Ramya Sunil
• Created: 09/Aug/11 22:45
• Updated: 25/Feb/12 13:57
• Resolved: 25/Feb/12 02:33

Description

appIDs, jobIDs and attempt/container ids are not consistently named in the logs, console and UI. For consistency purpose, they all have to follow a common naming convention.

Currently,
For appID
=========
On the RM UI: app_1308259676864_5
On the JHS UI: No appID
Console/logs: No appID
mapred-local dirs are named as: application_1308259676864_0005

For jobID
=========
On the RM UI: job_1308259676864_5_5
JHS UI: job_1308259676864_5_5
Console/logs: job_1308259676864_0005
mapred-local dirs are named as: No jobID

For attemptID
============
On the RM UI: attempt_1308259676864_5_5_m_24_0
JHS attempt_1308259676864_5_5_m_24_0
Console/logs: attempt_1308259676864_0005_m_000024_0
mapred-local dirs are named as: container_1308259676864_0005_000024