You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2016/04/12 14:22:25 UTC
[jira] [Comment Edited] (AURORA-955) more minimal http url to
determine aurora leader
[ https://issues.apache.org/jira/browse/AURORA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237062#comment-15237062 ]
Stephan Erb edited comment on AURORA-955 at 4/12/16 12:21 PM:
--------------------------------------------------------------
I believe this is now on master in form of a `/leaderhealth` endpoint. Details are available in the endpoint documentation: https://github.com/apache/aurora/blob/master/docs/reference/scheduler-endpoints.md#leader-health
was (Author: stephanerb):
I believe this is now on master in form of a `/leaderhealth` endpoint. Details are available in the endpoint documentation.
> more minimal http url to determine aurora leader
> ------------------------------------------------
>
> Key: AURORA-955
> URL: https://issues.apache.org/jira/browse/AURORA-955
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: alexius ludeman
> Priority: Minor
>
> it'd be nicer if there was a /leader which is http response 200 for leader, and non-200 for not.
> or maybe add additional body content to /health to indicate leader or "not leader"
> Right now the best solution is to parse the contents of /var for "framework_registered 1" or "scheduler_lifecycle_ACTIVE 1"
> the html body of /vars is ~50k.
> or if you fetch /scheduler and look for a redirect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)