[
https://issues.apache.org/jira/browse/YARN-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724403#comment-13724403
]
Hitesh Shah commented on YARN-988:
----------------------------------
The AM is only up while the job is running. Once the job is completed, the
tracker url redirects to the job history server.
What you probably want to do is look at the status of the application from the
initial /cluster/apps call to understand whether you are being redirected to
the AM or HistoryServer. Then again, there are likely to be race conditions
when the job is about to complete.
For job history, I believe this link should help:
http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/HistoryServerRest.html
It is an interesting issue that the url structure is different for AM vs
HistoryServer when it comes to accessing the rest interfaces. Maybe, that is
the issue to be solved for a layer accessing job information via the webservice
layer to work seamlessly.
> RM /proxy/app always gives HTML response
> ----------------------------------------
>
> Key: YARN-988
> URL: https://issues.apache.org/jira/browse/YARN-988
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Affects Versions: 2.1.0-beta
> Reporter: Srimanth Gunturi
>
> A call to [http://host:8088/ws/v1/cluster/apps] gives back JSON response of
> apps with trackingUrl of
> [http://host:8088/proxy/application_1375116837536_0003/jobhistory/job/job_1375116837536_0003].
>
> A GET call to this trackingUrl with {{Accept: application/json}} header
> always results in HTML output. It redirects (302) to
> [http://host:19888/jobhistory/job/job_1375116837536_0004/jobhistory/job/job_1375116837536_0004]
> where the output is always HTML.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
