aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1601) Add a flag to disable the HTTP redirect to the leader
Date Fri, 29 Jan 2016 17:42:39 GMT

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

Bill Farner commented on AURORA-1601:
-------------------------------------

Doesn't the scheduler have all the information needed to do the right thing without an additional
flag?

> Add a flag to disable the HTTP redirect to the leader
> -----------------------------------------------------
>
>                 Key: AURORA-1601
>                 URL: https://issues.apache.org/jira/browse/AURORA-1601
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Zameer Manji
>            Assignee: Joshua Cohen
>
> In an emergency scenario, it can be desirable to get a leading scheduler into the state
{{LEADER_AWAITING_REGISTRATION}} so a scheduler can be restored from backup.
> However in this state it is not possible to issue any RPCs to the API at this time because
the leader redirect filter redirects api requests: https://github.com/apache/aurora/blob/0eb753d1536ba8889eeb9fcf052b96b7b9f9c2a7/src/main/java/org/apache/aurora/scheduler/http/JettyServerModule.java#L260-L262
> Adding a flag to allow operators to disable this functionality would be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message