[SERVER-57373] Add new startup/upgrade warnings around eMRC=F removal Created: 02/Jun/21 Updated: 29/Oct/23 Resolved: 24/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Huayu Ouyang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2021-06-28 | ||||||||
| Participants: | |||||||||
| Description |
|
Add startup warnings around eMRC=F removal
Show warning message below for when customers with eMRC=f are upgrading to 5.0 (startup) **WARNING: Starting in 5.0, disabling enableMajorityReadConcern setting is no longer available because of MongoDB’s resiliency enhancements. If your environment was previously running with eMRC=f, please see https://docs.mongodb.com/v5.0/reference/read-concern-majority/#disable-read-concern-majority |
| Comments |
| Comment by Eric Reid [ 29/Dec/21 ] |
|
https://docs.mongodb.com/v5.0/reference/read-concern-majority/#disable-read-concern-majority does not seems to exist in v5.0 documentation. |
| Comment by Githook User [ 24/Jun/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |