[
https://issues.apache.org/jira/browse/MESOS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383186#comment-15383186
]
Anand Mazumdar commented on MESOS-3841:
---------------------------------------
[~clehene] We addressed this as part of V1 Operator API (in 1.0) i.e. we
introduced a new call {{GET_LEADING_MASTER}} that gives you information about
the current leader.
https://github.com/apache/mesos/blob/master/include/mesos/master/master.proto#L403
http://mesos.apache.org/documentation/latest/operator-http-api/
> 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: Jian Qiu
>
> 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)
