aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sweeney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-569) Current leading scheduler should be exposed via an endpoint
Date Wed, 02 Jul 2014 18:45:26 GMT

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

Kevin Sweeney commented on AURORA-569:
--------------------------------------

Upon investigation it looks like this behavior can be accomplished already via the LeaderRedirectFilter.
Doing a HEAD on any endpoint that has it applied will either get you a 302 to the leader or
a 200 if you're on the current leader.

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

Mime
View raw message