[
https://issues.apache.org/jira/browse/AURORA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050494#comment-14050494
]
Kevin Sweeney commented on AURORA-569:
--------------------------------------
Use case: All of a cluster's schedulers are in a round-robin DNS entry. Then a
script can hop through that entry until it gets a scheduler that will talk to
it, then use that scheduler to find the current leader and hit admin endpoints,
thrift api, etc.
> Current leading scheduler should be exposed via an endpoint
> -----------------------------------------------------------
>
> Key: AURORA-569
> URL: https://issues.apache.org/jira/browse/AURORA-569
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Kevin Sweeney
> Priority: Minor
>
> While discovering the leading scheduler via zookeeper is technically more
> correct, a following scheduler generally knows the location of the current
> leader. Expose an HTTP endpoint on the leader that allows an adhoc script to
> discover the leader without linking a zookeeper library
--
This message was sent by Atlassian JIRA
(v6.2#6252)
