1.3.0 Scheduler Java driver will work. @vinodkone
> On Sep 7, 2017, at 7:02 PM, Eli Jordan <elias.k.jor...@gmail.com> wrote: > > Ok, thanks Vinod > > So we need to upgrade then. I’m just looking at the new API, and the new > version of the java driver. > > I can see that the MesosSchedulerDriver class / Scheduler interface are still > available but there is also an additional v1 package for the new API. > > If I upgrade to libmesos v1.3.0 + mesos v1.3.0 of the scheduler java driver, > but continue to use the MesosSchedulerDriver / Scheduler APIs, will this be > compatible with a 1.3.0 mesos master? > Or, do I need to upgrade to the v1 scheduler API in order to be compatible? > >> On 8 Sep 2017, at 10:41 am, Vinod Kone <vinodk...@gmail.com> wrote: >> >> Could be. We don't guarantee backwards compatible between pre 1.0 components >> and post 1.0 components. Component here could be master/agent binaries, >> scheduler/executor libs and jars and eggs. >> >> @vinodkone >> >>> On Sep 7, 2017, at 3:25 PM, Eli Jordan <elias.k.jor...@gmail.com> wrote: >>> >>> Hi >>> >>> Is there an API version compatibility guide somewhere, describing what >>> versions of the scheduler API are compatible with which mesos master >>> versions? >>> >>> I'm asking because we have several frameworks using the 0.28.2 java based >>> scheduler driver, and recently upgraded our mesos masters and agents to >>> 1.3.0. >>> >>> The frameworks do work, but we have been seeing some issues around >>> reconciliation that we weren't seeing before. Could this be related to a >>> scheduler driver incompatibility? >>> >>> Thanks >>> Eli >
