[SERVER-45796] MongoDB 4.2 ability to specify FCV 4.0 before first startup Created: 27/Jan/20 Updated: 06/Dec/22 Resolved: 11/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Emilio Scalise | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Do | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
There are some circumstances where the newer MongoDB 4.2 FCV 4.2 Ops Manager backups may not be desired by the customer. When deploying a new MongoDB 4.2.x instance the data files are created by default using FCV 4.2. Currently the best and cleanest way to run MongoDB 4.2.x FCV 4.0 data files when deploying a new instance is:
It would be nice to have a way to configure MongoDB to create FCV 4.0 data files at startup. |
| Comments |
| Comment by Craig Homa [ 11/Feb/20 ] |
|
emilio.scalise the Query team doesn't feel that this is the right thing to do without additional context. Please re-open with additional details if you disagree. |
| Comment by Carl Champain (Inactive) [ 27/Jan/20 ] |
|
Passing this ticket along to the appropriate team. |