[jira] [Updated] (MESOS-5936) Operator SUBSCRIBE api should provdide more task metadata than just state changes

["Zhitao Li (JIRA)" <ji...@apache.org>]

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

Zhitao Li updated MESOS-5936:
-----------------------------
    Shepherd: Anand Mazumdar

> Operator SUBSCRIBE api should provdide more task metadata than just state changes
> ---------------------------------------------------------------------------------
>
>                 Key: MESOS-5936
>                 URL: https://issues.apache.org/jira/browse/MESOS-5936
>             Project: Mesos
>          Issue Type: Improvement
>          Components: HTTP API, json api
>    Affects Versions: 1.0.0
>            Reporter: Steven Schlansker
>            Assignee: Zhitao Li
>              Labels: mesosphere
>             Fix For: 1.1.0
>
>
> I am starting to use the new Operator event subscription API to get notified of task changes.  The initial TASK_STAGING event has a good amount of information, but unfortunately future events like TASK_RUNNING include almost no metadata.  This means that any task information that cannot be determined until the task launches (in my particular case, the IP address assigned by the Docker containerizer) is not available through the event stream.
> Here is a gist of a single task that was launched, comparing the information in 'state.json' vs the subscribed events:
> https://gist.github.com/stevenschlansker/c1d32aa9ce37a73f9c4d64347397d3b8
> Note particularly how the IP address never shows in the event stream.
> Task updates should expose the task information that changed.  If this is too onerous, maybe the subscription call can take optional sets of data to include, with the first one being additional task metadata.
> A possible workaround is to use the task events to fetch 'state.json' separately, but this is inherently racy and totally undermines the utility of the event stream api.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)