Upgrade to mesos 1.6.1 and fork of mesos-rxjava #1867
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
built and pushed |
Member
Author
|
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 |
Member
Author
|
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 |
Member
Author
|
Note for posterity, not going all the way to 1.7 because it requires a higher minimum docker version than we are running |
Contributor
|
🚢 |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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