You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2014/12/03 01:10:12 UTC

[jira] [Commented] (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=14232330#comment-14232330 ] 

Maxim Khutornenko commented on AURORA-955:
------------------------------------------

FYI, there is an admin command to get the leading scheduler, e.g.: {{$ aurora_admin get_scheduler devcluster}}

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