You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Subroto Sanyal (Assigned) (JIRA)" <ji...@apache.org> on 2011/12/17 11:20:31 UTC
[jira] [Assigned] (MAPREDUCE-2793) [MR-279] Maintain consistency in
naming appIDs, jobIDs and attemptIDs
[ https://issues.apache.org/jira/browse/MAPREDUCE-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subroto Sanyal reassigned MAPREDUCE-2793:
-----------------------------------------
Assignee: Subroto Sanyal
> [MR-279] Maintain consistency in naming appIDs, jobIDs and attemptIDs
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-2793
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2793
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Subroto Sanyal
> Priority: Blocker
> Fix For: 0.24.0
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira