[SERVER-36982] Reintroduce enableMajorityReadConcern:false server parameter Created: 04/Sep/18 Updated: 29/Oct/23 Resolved: 24/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWNA | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 2018-09-10, Repl 2018-09-24, Repl 2018-10-08 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||
| Description |
|
The enableMajorityReadConcern:false option exists on 3.6, to allow the server to avoid holding on to all history since the majority commit point. We would like to add this option on 4.0 to address pain due to commit point lag in replica sets with arbiters. This work should include adding the enableMajorityReadConcern:false Evergreen variant to 4.0, which was introduced inĀ |
| Comments |
| Comment by Githook User [ 25/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |
| Comment by Githook User [ 24/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |