You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Zhitao Li (JIRA)" <ji...@apache.org> on 2018/03/06 17:00:00 UTC

[jira] [Commented] (MESOS-8641) New heartbeat on event stream could change the behavior for subscriber

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

Zhitao Li commented on MESOS-8641:
----------------------------------

Attempt to fix: 

https://reviews.apache.org/r/65930

> New heartbeat on event stream could change the behavior for subscriber
> ----------------------------------------------------------------------
>
>                 Key: MESOS-8641
>                 URL: https://issues.apache.org/jira/browse/MESOS-8641
>             Project: Mesos
>          Issue Type: Bug
>          Components: HTTP API
>    Affects Versions: 1.5.0
>            Reporter: Zhitao Li
>            Assignee: Zhitao Li
>            Priority: Major
>
> A new event for heartbeat is added in [MESOS-7695|https://reviews.apache.org/r/61262/bugs/MESOS-7695/], but I believe the implementation in [https://reviews.apache.org/r/61262/] can trigger a corner case and send *_HEARTBEAT_* before _*SUBSCRIBED*_
>  
> I would consider this a behavior change for the customer and I propose we change the order as I suggest in the review to preserve previous behavior (since the subscriber needs to see the _*SUBSCRIBED*_ event to really know how it should respond to *_HEARTBEAT_* message anyway)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)