[jira] [Commented] (MESOS-6066) Operator SUBSCRIBE api should include timestamps

["Anand Mazumdar (JIRA)" <ji...@apache.org>]

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

Anand Mazumdar commented on MESOS-6066:
---------------------------------------

We intend to expose the {{TaskStatus}} as part of the {{TaskUpdated}} event. That would have the timestamp details.

> Operator SUBSCRIBE api should include timestamps
> ------------------------------------------------
>
>                 Key: MESOS-6066
>                 URL: https://issues.apache.org/jira/browse/MESOS-6066
>             Project: Mesos
>          Issue Type: Bug
>          Components: HTTP API, json api
>    Affects Versions: 1.0.0
>            Reporter: Steven Schlansker
>
> Events coming from the Mesos master are delivered asynchronously.  While usually they are processed in a timely fashion, it really scares me that updates do not have a timestamp:
> {code}
> 301
> {
>   "task_updated": {
>     "agent_id": {
>       "value": "fdbb3ff5-47c2-4b49-a521-b52b9acf74dd-S14"
>     },
>     "framework_id": {
>       "value": "Singularity"
>     },
>     "state": "TASK_KILLED",
>     "task_id": {
>       "value": "pp-demoservice-steven.2016.07.05T17.00.06-1471901722511-1-mesos_slave17_qa_uswest2.qasql.opentable.com-us_west_2b"
>     }
>   },
>   "type": "TASK_UPDATED"
> }
> {code}
> Events should have a timestamp that indicates the time that they happened at, otherwise your timestamps include delivery and processing delays.



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