mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Harutyunyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3841) Master HTTP API support to get the leader
Date Fri, 13 Nov 2015 16:09:11 GMT

     [ https://issues.apache.org/jira/browse/MESOS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Artem Harutyunyan updated MESOS-3841:
-------------------------------------
    Assignee:     (was: 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
>
> 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)

Mime
View raw message