[ 
https://issues.apache.org/jira/browse/AURORA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashwin Murthy updated AURORA-1493:
----------------------------------
                 Flags: Patch
                Labels: uber  (was: )
    Remaining Estimate: 48h
     Original Estimate: 48h

https://reviews.apache.org/r/45511/

> create ELB-friendly endpoint to detect leading scheduler
> --------------------------------------------------------
>
>                 Key: AURORA-1493
>                 URL: https://issues.apache.org/jira/browse/AURORA-1493
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler, Usability
>            Reporter: brian wickman
>            Assignee: Ashwin Murthy
>              Labels: uber
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> iiuc hitting the web ui for non-leading schedulers redirects to the leader.  
> this doesn't really help the members of the ensemble are not publicly 
> routable.
> if there was a /leader endpoint that returned "200 OK" if it is leader and 
> some 3xx/4xx code if not, then it would be easier to configure an ELB to 
> route traffic to the correct leader, simplifying the use of aurora in an AWS 
> deployment.



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

Reply via email to