You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/02/12 22:58:19 UTC
[jira] [Comment Edited] (AURORA-211) Scheduler UI should redirect
to the current leader
[ https://issues.apache.org/jira/browse/AURORA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899639#comment-13899639 ]
Bill Farner edited comment on AURORA-211 at 2/12/14 9:57 PM:
-------------------------------------------------------------
FWIW this is a regression with the move to the new web UI. {{LeaderRedirectFilter.java}} has been responsible for this behavior.
was (Author: wfarner):
FWIW this is a regression with the move to the new web UI. {{LeaderRedirect.java}} has been responsible for this behavior.
> Scheduler UI should redirect to the current leader
> --------------------------------------------------
>
> Key: AURORA-211
> URL: https://issues.apache.org/jira/browse/AURORA-211
> Project: Aurora
> Issue Type: Story
> Components: Scheduler, UI, Usability
> Reporter: Kevin Sweeney
> Priority: Minor
>
> Right now if the scheduler is running in a high-availability mode and you land on a node that isn't the leader you'll get an error page with
> {noformat}
> An error occurred when querying the server. Please reload this page.
> Storage is not READY
> {noformat}
> Instead, similar to mesos we should redirect to the leader if one exists.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)