[
https://issues.apache.org/jira/browse/MAPREDUCE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778242#action_12778242
]
Jothi Padmanabhan commented on MAPREDUCE-1185:
----------------------------------------------
In the test case, does it also make sense to add one more check -- do not set
{{conn.setInstanceFollowRedirects(false)}} and then ensure that
{{conn.connect()}} is successful. If not the contents, we would at least verify
that the redirection works as expected, no?
> 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
>
>
> 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.
