[SERVER-62214] Use explicit read concern in InitialSyncer and CollectionCloner Created: 21/Dec/21 Updated: 29/Oct/23 Resolved: 18/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Gabriel Marks |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Security 2022-01-24 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 15 | ||||||||||||||||
| Description |
|
When investigating BF-23599, I noticed we use ImplicitDefault read concern to get the top of the oplog and also to read the collection data in the logical initial syncer. Since the default read concern can be changed by the user, we probably want to use an explicit read concern ("local" or "available") This doesn't cause BF-23599 because the default read concern in that test was already "local". |
| Comments |
| Comment by Githook User [ 18/Jan/22 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |