[
https://issues.apache.org/jira/browse/MESOS-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326647#comment-14326647
]
Kapil Arya edited comment on MESOS-2371 at 2/19/15 1:02 AM:
------------------------------------------------------------
Created a RR: https://reviews.apache.org/r/31162/
Tested with master running HEAD with this patch, and slave running 0.21.0 with
src/test-framework.
The tests succeed when src/test-framework is running from the same version as
the slave. However, if I run src/test-framework from the master version, it
doesn't succeed and errors out with unexpected TASK_LOST. Not sure if this is
the desired behavior.
EDIT: The TASK_LOST issue was a local configuration issue and was fixed once
LD_LIBRARY_PATH was adjusted to point to the correct location
was (Author: karya):
Created a RR: https://reviews.apache.org/r/31162/
Tested with master running HEAD with this patch, and slave running 0.21.0 with
src/test-framework.
The tests succeed when src/test-framework is running from the same version as
the slave. However, if I run src/test-framework from the master version, it
doesn't succeed and errors out with unexpected TASK_LOST. Not sure if this is
the desired behavior.
> Removing internal namespace for protobufs results in incompatible upgrade
> -------------------------------------------------------------------------
>
> Key: MESOS-2371
> URL: https://issues.apache.org/jira/browse/MESOS-2371
> Project: Mesos
> Issue Type: Bug
> Reporter: Jie Yu
> Assignee: Kapil Arya
> Priority: Blocker
>
> This bug is introduced this ticket:
> https://issues.apache.org/jira/browse/MESOS-2272
> where we removed internal namespace for all our protobuf messages. For
> example: mesos::internal::AuthenticateMessage -> mesos::AuthenticateMessage
> As a result, the new master/slave (0.22.0) will drop all messages from old
> master/slave (0.21.0) because the protobuf message type name does not match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
