WIP: Improve documentation about converting from MMAPv1 to WiredTiger #6204
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
* DOCSP-15476-reapply-53-release-note-geoNear * DOCSP-15476-reapply-53-release-note-geoNear Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com>
* Add note about extra DBRef fields * Incorporating external review comments
* adds field descriptions * style guide fix
mongo-cr-bot
pushed a commit
that referenced
this pull request
Feb 2, 2024
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.
A story about upgrading:
I just learned that I needed to upgrade MongoDB for a different program to be able to update. No big deal, I'll just go read the steps to upgrade Mongo from v4.0.something.
Ok, gotta add a new apt-source for v... and it wasn't self updating to 4.2... weird. Whatever.
Hmmm, what is this mmapv1 thing? Oh, it's just the default storage type. I just used defaults. Find by me if it gets upgraded to the latest.
apt upgradeinstalls new version...mongodservice is still running... weird. Usually apt takes care of that.sudo systemctl restart mongod... Wait, it's not coming back up...No error in syslog... oh right, mongo does it's own logs. Hmmm, mmapv1 support was removed so now it can't start. Weird. Ok, find the migration instructions, basically:
mongodump --out=mongo.dump && ...Wait, mongo needs to be running for the dump to work. Now I need to downgrade and I don't remember exactly which version was running before...Now I'm frustrated. Clearly I've done this to myself but it sure feels like the docs could have had a simple yet clear warning on the migration page that you can't miss: "Export/Dump before stopping the dameon/upgrading!"
So, here I am making a request to change the docs to save others from the trouble I went through in the hopes that someone will see this and agree.
Ps, Unfortunately, this repo doesn't allow "Issues", so I've had to create a bogus "Pull Request" as I don't see any other way to give feedback.
Alternatively, I don't see how mongod can't just automatically do the right thing here. Refusing to write/update a mmapv1 database is reasonable to get users to upgrade but now it can't even read it?!?