Hi Hendrik, mesos-rxjava has had a 0.1.0 release published to maven central.
It's primary focus is to provide an event stream and sink for reading events from mesos and sending calls to mesos. So far it only takes care of HTTP connection, stream identification, codec for mesos protos and sending calls back to mesos. There are also some useful tools and utilities for testing scheduler code. There is no automatic reconnect or retry if the connection to the master is lost. It does however propagate and connection failures up to the application so the application can decide if it wants to reconnect or not. And will handle master redirection when connecting, so in many scenarios the stream will just have to be re-opened with an updated subscribe call and things will plug along. Full javadocs for mesos-rxjava can be found here: https://mesosphere.github.io/mesos-rxjava/javadocs/0.1.0/ There is also an example scheduler: https://github.com/mesosphere/mesos-rxjava/blob/v0.1.0/mesos-rxjava-example/mesos-rxjava-example-framework/src/main/java/com/mesosphere/mesos/rx/java/example/framework/sleepy/Sleepy.java#L55 Hope this helps On Tue, Aug 23, 2016 at 1:38 PM, Vinod Kone <[email protected]> wrote: > +Ben Whitehead > > As the Apache Mesos project, we decided to not have "official" (HTTP) API > libraries in the repo (http://github.com/apache/mesos), going forward. > > As for mesos-rxjava, I'm not sure of its production readiness. Ben > Whitehead (it's maintainer) might be able to shed more light on its status. > > I don't think Jesos speaks the new HTTP API. > > On Tue, Aug 23, 2016 at 1:19 PM, Hendrik Haddorp <[email protected]> > wrote: > >> Is there any official Java binding available for that? So far I found >> these: >> https://github.com/mesosphere/mesos-rxjava >> https://github.com/groupon/jesos >> >> Jesos seems to only be build against Mesos 0.22.0. >> Do you know if Mesos RxJava looks very current but also quite different >> from the old Java API. Is this going to be the new official Java API, >> given that it is from Mesosphere? Any idea if this can handle Mesos >> master fail overs like the old one should be able to do? >> >> On 23/08/16 21:13, Vinod Kone wrote: >> > If you are writing a new scheduler, I would highly recommend using the >> > new HTTP API instead of the Java bindings. This would eliminate the >> > dep on the native library. >> > >> > If you still want to use the old bindings, the easiest way might be to >> > install mesos deb package in your docker image. >> > >> > On Tue, Aug 23, 2016 at 11:27 AM, Hendrik Haddorp >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > Hi, >> > >> > I wrote a Mesos scheduler using the Java bindings, which worked >> > great so >> > far. Now I would like to run my scheduler as a docker container on >> > Marathon. The problem is now that I'm missing the required native >> > libraries. What is the best way to install them (in Ubuntu) without >> > pulling heaps of other stuff? >> > >> > Thanks, >> > Hendrik >> > >> > >> >> >
