[
https://issues.apache.org/jira/browse/AMBARI-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978966#comment-14978966
]
DIPAYAN BHOWMICK commented on AMBARI-13612:
-------------------------------------------
Added two proxy resources for RM and ATS. Rather than directly hitting the RM
or ATS url, this endpoints has to be hit. The example is give below:
RM endpoint: <RM
URL>/proxy/application_1440170009955_0020/ws/v1/tez/dagProgress?dagID=1
Proxy RM endpoint:
<INSTANCE_RESOURCE_URL>/rmproxy/application_1440170009955_0020/ws/v1/tez/dagProgress?dagID=1
ATS endpoint: <ATS URL>/ws/v1/timeline/TEZ_DAG_ID?limit=1
Proxy ATS endpoint:
<INSTANCE_RESOURCE_URL>/atsproxy/ws/v1/timeline/TEZ_DAG_ID?limit=1
The proxy will only honor 200 status code from the RM and ATS endpoints. Any
other status code will be considered as an error and it will intercepted and
returned back as failure with the same status code that RM or ATS sends.
> Add RM and ATS Proxy Urls to Ambari Tez
> ---------------------------------------
>
> Key: AMBARI-13612
> URL: https://issues.apache.org/jira/browse/AMBARI-13612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.1.3
>
> Attachments: AMBARI-13612_branch-2.1.patch
>
>
> Everytime the active went down and the standby is becoming active, the app
> details page in Tez shows a blank page. A refresh fixes the issue but it is
> likely due to the status call throwing an error.
> This happens because, Tez view caches the RM and ATS Url in the frontend and
> uses it for querying the rest of the time. So, when the active RM changes,
> the call still hits the standby/killed RM and hence the UI fails.
> As for the solution, the Tez view will not cache the Urls rather query the
> proxy url to talk to RM and ATS and the ATS/RM Url will be fetched every time
> from within the proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
