Skip to content
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 mongodb to 5.0 #1568

Closed
6 tasks
longrunningprocess opened this issue Oct 28, 2022 · 4 comments · Fixed by #1633
Closed
6 tasks

upgrade mongodb to 5.0 #1568

longrunningprocess opened this issue Oct 28, 2022 · 4 comments · Fixed by #1633
Assignees
Labels
engineering Tasks which do not directly relate to a user-facing feature or fix

Comments

@longrunningprocess
Copy link
Contributor

longrunningprocess commented Oct 28, 2022

Is your feature request related to a problem? Please describe.

There is a desire to utilize aggregation pipelines and take advantage of possible perf improvements.

Additional context
https://www.mongodb.com/docs/v5.0/release-notes/4.4-upgrade-standalone/

see #1567 for history of upgrades so far

  • verify mongodb PECL extension is recent enough
  • verify mongodb PHP library (composer) is recent enough
  • verify compatibility version is set to 4.4 initially
  • verify clean mongod service shutdown
  • take a volume snapshot before upgrading
  • setFeatureCompatibilityVersion: "5.0" for every db
@megahirt
Copy link
Collaborator

Thanks for this! Let's plan to upgrade to 5.0 sometime in the second half of November. That should allow 4.4 to run in production a few weeks to make sure there are no issues before going up again.

@megahirt
Copy link
Collaborator

The upgrade guide from 4.4 -> 5.0 is here: https://www.mongodb.com/docs/v5.0/release-notes/5.0-upgrade-standalone/

@megahirt
Copy link
Collaborator

We need to verify the PECL extension and composer library are compatible with MongoDB 5.0. See this table: https://www.mongodb.com/docs/drivers/php/#compatibility-table-legend
image

@megahirt
Copy link
Collaborator

Also, it looks like we need to run

db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } ) 

on every database after the container has been upgraded.

They also make mention of ensuring that mongodb 4.4 has a clean shutdown...not sure how we can verify that or not

@megahirt megahirt added engineering Tasks which do not directly relate to a user-facing feature or fix dependencies and removed dependencies labels Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Tasks which do not directly relate to a user-facing feature or fix
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants