[ 
https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868563#comment-13868563
 ] 

Cindy Li commented on YARN-1525:
--------------------------------

In practice, users mostly go to the RM webUI to see their application's status. 
I want to get some comments for the two different designs: 

Proposal 1. When a user enters the index page's url of the standby RM,  user 
will be redirected to that of the active RM. so user will stay in the webUI of 
the active RM after redirection. 
eg: if a user enters standby RM's url: http://localhost:23188/
he/she will be redirect to http://localhost:33188/


Proposal 2. Redirect some pages only when user clicks on them. 
eg: when user enters standby RM's url: http://localhost:23188/
actually by default it currently goes to http://localhost:23188/cluster. As 
this page shows application information, the standby RM needs to get that from 
the active RM. If we don't redirect that to the active RM's url 
http://localhost:33188/cluster, as proposal 1 does, we'll have to retrieve that 
information from the active RM, either through active RM's web service or 
through RPC calls. The speed of this is not as good as letting users go to that 
page directly.   

@Karthik, can you comment on keeping HA state info based on the two different 
proposals above? Proposal 1 looks more convenient for cluster users (who submit 
jobs and want to see job info) and has nearly no performance impact on standby 
RM or active RM. Proposal 2 looks more costly than proposal 1.

> Web UI should redirect to active RM when HA is enabled.
> -------------------------------------------------------
>
>                 Key: YARN-1525
>                 URL: https://issues.apache.org/jira/browse/YARN-1525
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Cindy Li
>
> When failover happens, web UI should redirect to the current active rm.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to