You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Ashwin Murthy (JIRA)" <ji...@apache.org> on 2016/02/22 19:44:18 UTC

[jira] [Assigned] (AURORA-1493) create ELB-friendly endpoint to detect leading scheduler

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

Ashwin Murthy reassigned AURORA-1493:
-------------------------------------

    Assignee: Ashwin Murthy

> 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
>
> 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)