[
https://issues.apache.org/jira/browse/MAPREDUCE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782307#action_12782307
]
Sharad Agarwal commented on MAPREDUCE-1185:
-------------------------------------------
bq. 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. This will require a map
between job ids and the file name to be kept inside the jobtracker,
Since URL is given by the JobClient API, the thinking was that users don't
really need to bother about the contents and map based thing will not survive
JT restarts. The long term solution being done by MAPREDUCE-323. Saying that it
looks like (also based on off line discussion with Arun) that map based
solution is acceptable in medium term until MAPREDUCE-323 is done.
bq. but that should not be too big, since the entries can be removed when job
history is purged periodically. Makes sense ?
Yes, that should work. The only problem we also need to keep in mind that when
history cleaner thread runs, it does a listing of the files in history folder
and deletes the ones which are older than 30 days (default). But in the
meanwhile operations could have manually purged the files. So those entries
won't be purged from the map. To address this timestamp can be maintained along
with the history file name.
> 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.
