[jira] [Commented] (MESOS-5571) Scheduler JNI throws exception when the major versions of JAR and libmesos don't match

["Yan Xu (JIRA)" <ji...@apache.org>]

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

Yan Xu commented on MESOS-5571:
-------------------------------

Backported to 0.28.3 and 0.27.4.

> Scheduler JNI throws exception when the major versions of JAR and libmesos don't match
> --------------------------------------------------------------------------------------
>
>                 Key: MESOS-5571
>                 URL: https://issues.apache.org/jira/browse/MESOS-5571
>             Project: Mesos
>          Issue Type: Bug
>          Components: java api
>    Affects Versions: 1.0.0
>            Reporter: Yan Xu
>            Assignee: Yan Xu
>            Priority: Blocker
>             Fix For: 0.28.3, 1.0.0, 0.27.4
>
>
> In [convert.cpp|https://github.com/apache/mesos/blob/master/src/java/jni/convert.cpp#L153] we compare the major versions of the native library and the jar. This makes upgrading frameworks unnecessarily hard because you would have to deploy Mesos and frameworks in lockstep.
> Backwards-incompatible changes would warrant a major version bump but not
> vise versa. Plus it's more standard to express and check dependency
> versions outside of the code but through package metadata.
> The proposed solution is to remove this major version check altogether.



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