[
https://issues.apache.org/jira/browse/MAPREDUCE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782062#action_12782062
]
Milind Bhandarkar commented on MAPREDUCE-1185:
----------------------------------------------
I think the approach of including the job history file name in the URL since
the beginning will cause more headaches, since the job history file name
includes some things that are unparseable by humans. It may be easier and more
human-friendly to translate the job id internally to the history file name, and
return the content of job history. This will require a map between job ids and
the file name to be kept inside the jobtracker, but that should not be too big,
since the entries can be removed when job history is purged periodically. Makes
sense ?
In any case, Hadoop 0.21 will have a different human-friendly file naming
scheme, when this can go away.
> URL to JT webconsole for running job and job history should be the same
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-1185
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1185
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Attachments: 1185_v1.patch, 1185_v2.patch, 1185_v3.patch,
> 1185_v4.patch
>
>
> The tracking url for running jobs and the jobs which are retired is
> different. This creates problem for clients which caches the job running url
> because soon it becomes invalid when job is retired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
