-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to mesos 1.6.1 and fork of mesos-rxjava #1867
Conversation
built and pushed |
In local testing, Singularity running 1.6.1 could still effectively communicate with a 1.1.0 mesos master. Will also check the reverse to determine best upgrade order. As normal, slaves/executors should likely be last |
Upgrading master/scheduler in either order works fine. new executor (1.6.1) seems to be able to run fine on old mesos (1.1.0) hosts as well |
Note for posterity, not going all the way to 1.7 because it requires a higher minimum docker version than we are running |
🚢 |
We ran into a few network partition bugs with the mesos master that are fixed in later versions. This will allow us to update to mesos 1.6.1. Mesos 1.6 uses protobuf 3, which means we also had to upgrade mesos-rxjava. Since the project is seemingly abandoned, we now have our own fork at https://github.com/HubSpot/mesos-rxjava, which is now updated with the newer mesos and protobuf versions. PR still needs a good bit of testing