[
https://issues.apache.org/jira/browse/MAPREDUCE-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved MAPREDUCE-3052.
--------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 0.24.0)
(was: 0.23.0)
Duplicate of MAPREDUCE-2793
> Maintain consistency in naming appIDs, jobIDs and attemptIDs
> ------------------------------------------------------------
>
> Key: MAPREDUCE-3052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Jeffrey Naisbitt
> Assignee: Jeffrey Naisbitt
>
> Currently, the appIDs, jobIDs and attempt/container ids are not consistently
> named in the logs, console and
> UI.
> Some recent jiras have fixed the inconsistencies with the appID.
> 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
> I am planning on changing the jobID to match job_1308259676864_0005 in the RM
> UI and the JHS UI.
> 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
> I'm not sure the best way to handle the attempt and container IDs, but I'm
> making them more consistent. (If any of you have preferences, let me know)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
