[
https://issues.apache.org/jira/browse/MESOS-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596891#comment-14596891
]
Benjamin Mahler commented on MESOS-2909:
----------------------------------------
I have a patch for this, but will hold off until we have the handlers fully
implemented on the driver / library side (linked in blocking tickets, but more
will follow). Adding it after the handlers are functional allows the master to
assume that a present version means events can be sent.
> Add version field to RegisterFrameworkMessage and ReregisterFrameworkMessage
> ----------------------------------------------------------------------------
>
> Key: MESOS-2909
> URL: https://issues.apache.org/jira/browse/MESOS-2909
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Benjamin Mahler
>
> In the same way we added 'version' field to RegisterSlaveMessage and
> ReregisterSlaveMessage, we should do it framework (re-)registration messages.
> This would help master determine which version of scheduler driver it is
> talking to.
> We want this so that master can start sending Event messages to the scheduler
> driver (and scheduler library). In the long term, master will send a
> streaming response to the libraries, but in the meantime we can test the
> event protobufs by sending Event messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
