Pin bundled mongo to 2.6 to avoid in-place upgrade woes #2361
Conversation
This file contains 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
sandstorm-84 and earlier shipped mongo 2.4, which creates its auth schema in a different way than mongo 2.6 and above. While mongo 2.6 is able to read said schema, mongo 3.2 is not. To avoid breaking servers that were originally installed with mongo 2.4, we can't jump to mongo 3.2 just yet. Mongo 2.6 is still fine, and Meteor remains backwards-compatible with Mongo 2.6, so we can continue shipping this for a while. This change makes make-bundle.sh cache a copy of sandstorm-171 (the latest release as of this writing) and copy its mongo/mongod into the new bundle, rather than pulling those binaries from the current Meteor dev bundle.
|
I tried this out on my server. It appears to work. |
This way, git won't list the file in `git status` and `make clean` won't wipe it out and force you to re-download the bundle.
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.
sandstorm-84 and earlier shipped mongo 2.4, which creates its auth schema in a
different way than mongo 2.6 and above. While mongo 2.6 is able to read said
schema, mongo 3.2 is not.
To avoid breaking servers that were originally installed with mongo 2.4, we
can't jump to mongo 3.2 just yet. Mongo 2.6 is still fine, and Meteor remains
backwards-compatible with Mongo 2.6, so we can continue shipping this for a while.
This change makes make-bundle.sh cache a copy of sandstorm-171 (the latest
release as of this writing) and copy its mongo/mongod into the new bundle,
rather than pulling those binaries from the current Meteor dev bundle.
Additional notes on mongo upgrades: