You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Guangya Liu (JIRA)" <ji...@apache.org> on 2015/11/08 02:48:10 UTC
[jira] [Assigned] (MESOS-3841) Master HTTP API support to get the
leader
[ https://issues.apache.org/jira/browse/MESOS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guangya Liu reassigned MESOS-3841:
----------------------------------
Assignee: Guangya Liu
> Master HTTP API support to get the leader
> -----------------------------------------
>
> Key: MESOS-3841
> URL: https://issues.apache.org/jira/browse/MESOS-3841
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
> Reporter: Cosmin Lehene
> Assignee: Guangya Liu
>
> There's currently no good way to query the current master ensemble leader.
> Some workarounds to get the leader (and parse it from leader@ip) from {{/state.json}} or to grep it from {{master/redirect}}.
> The scheduler API does an HTTP redirect, but that requires an HTTP POST coming from a framework as well
> {{POST /api/v1/scheduler HTTP/1.1}}
> There should be a lightweight API call to get the current master.
> This could be part of a more granular representation (REST) of the current state.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)