Avidan Ackerson created MESOS-4913:
--------------------------------------
Summary: Mesos UI should call leader for data rather than redirect
if non-leader
Key: MESOS-4913
URL: https://issues.apache.org/jira/browse/MESOS-4913
Project: Mesos
Issue Type: Improvement
Reporter: Avidan Ackerson
Currently, when you go to a mesos master that isn't the leader, the UI
redirects you to the actual leader by using a JavaScript call to go to
/master/redirect. However, this redirection causes many problems for systems
doing load balancing through nginx (for example). Although access to the master
can be handled via a firewall, if the master hit isn't the actual leader, the
redirect will now point the browser to the new page and is now no longer behind
firewall protection.
This was a feature proposed in MESOS-1865 because the non-leaders were
returning empty data that was meaningless to the user. By the same token, the
UI shows no useful data when it's not the leader.
But as far as the UI is concerned, why do we need a redirection in the first
place? Wouldn't it be easier to just call the leader for the data and display
it in the UI? Then, instead of forcing a redirection, we can just have an
informational dialog saying that it's not the leader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)