Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

New Upgrade Scenario for MongoDB Engine Upgrade from MMAPv1 to WiredTiger #372

Open
devendra104 opened this issue Sep 24, 2019 · 1 comment
Assignees

Comments

@devendra104
Copy link
Member

I would like to add Mongo storage engine upgrade test scenario in the current upgrade(Satellite, Capsule, and CustomerDB upgrade) workflow. There is no impact on the current workflow if we include it and will achieve both the things (upgrade and mongo DB engine upgrade) in a single attempt.
We will keep it separately in current upgrade workflow and it will be executed in end of the upgrade. Mongo DB engine upgrade treats as an optional parameter, If the user wants to test MongoDB Engine upgrade along with upgrade then pass the optional parameter(like foreman-maintain, puppet version) in the current workflow.

In this release, We have observed 8 to 9 bugs which were related to this feature.
As of now, mongo DB engine upgrades as an optional parameter of an upgrade and by default it uses MMAPv1 mongo DB engine.

@ntkathole
Copy link
Contributor

@devendra104 is it part of upgrade process now or do we need to include in CI/any task?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants