hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iyappan Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1185) URL to JT webconsole for running job and job history should be the same
Date Tue, 01 Dec 2009 10:57:20 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784173#action_12784173
] 

Iyappan Srinivasan commented on MAPREDUCE-1185:
-----------------------------------------------

Testing completed with new patch. All testcases pased:
+1 for QA.

Scenarios tested:

Change the mapred.job.tracker.history.completed.location to point to a local file system directory

1) Run some jobs like sleep, randomwriter, streaming job and see if their job URI gets redirected
to the done folder
after the jobs are retired.

2) Run multiple jobs and see if still the jobs are getting redirected properly.

3) Do a  JT restart and then type the jobid URL (not the done folder URL) of the job before
the JT restart and see if
it gives proper error.

4) Change the mapred.job.tracker.history.completed.location to point to a dfs directory and
then run steps 1,2,3 and
see if it works properly.



> 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, 1185_v5.patch,
patch-1185-1-ydist.txt, patch-1185-2-ydist.txt, patch-1185-ydist.txt
>
>
> 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.


Mime
View raw message