aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1655) Update endpoints.md documentation page for all scheduler HTTP endoints
Date Fri, 01 Apr 2016 02:46:25 GMT

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

Ashwin Murthy commented on AURORA-1655:
---------------------------------------

As part of 1493, we added the new endpoints.md page under docs/operations. We need to update
this to include the various other HTTP endpoints as well

> Update endpoints.md documentation page for all scheduler HTTP endoints
> ----------------------------------------------------------------------
>
>                 Key: AURORA-1655
>                 URL: https://issues.apache.org/jira/browse/AURORA-1655
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler, Usability
>            Reporter: Ashwin Murthy
>            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)

Mime
View raw message