mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitrii Rozhkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-8078) Some fields went missing with no replacement in api/v1
Date Thu, 07 Dec 2017 17:33:00 GMT

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

Dmitrii Rozhkov updated MESOS-8078:
-----------------------------------
    Description: 
Hi friends, 

These fields are available via the state.json but went missing in the v1 of the API:
-leader_info- -> available via GET_MASTER which should always return leading master info
start_time
elected_time

As we're showing them on the Overview page of the DC/OS UI, yet would like not be using state.json,
it would be great to have them somewhere in V1.

  was:
Hi friends, 

These fields are available via the state.json but went missing in the v1 of the API:
leader_info
start_time
elected_time

As we're showing them on the Overview page of the DC/OS UI, yet would like not be using state.json,
it would be great to have them somewhere in V1.


> Some fields went missing with no replacement in api/v1
> ------------------------------------------------------
>
>                 Key: MESOS-8078
>                 URL: https://issues.apache.org/jira/browse/MESOS-8078
>             Project: Mesos
>          Issue Type: Story
>          Components: HTTP API
>            Reporter: Dmitrii Rozhkov
>            Assignee: Vinod Kone
>              Labels: mesosphere
>
> Hi friends, 
> These fields are available via the state.json but went missing in the v1 of the API:
> -leader_info- -> available via GET_MASTER which should always return leading master
info
> start_time
> elected_time
> As we're showing them on the Overview page of the DC/OS UI, yet would like not be using
state.json, it would be great to have them somewhere in V1.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message