[
https://issues.apache.org/jira/browse/AURORA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746036#comment-14746036
]
brian wickman commented on AURORA-1493:
---------------------------------------
it ignores anything but 200 OK. a redirect wouldn't really be useful (most
likely the host/ip being redirected is an internal host/ip) but i think the LB
would just ignore that.
> 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
>
> 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)
