[jira] [Commented] (MESOS-3841) Master HTTP API support to get the leader

["Cosmin Lehene (JIRA)" <ji...@apache.org>]

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

Cosmin Lehene commented on MESOS-3841:
--------------------------------------

[~haosdent@gmail.com] I mentioned the {{/redirect}} endpoint in the original issue description, however, I didn't consider parsing the HTTP header of a 307 to be a normal way to get some metadata about the cluster leader. 

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