[SERVER-74598] Commands without explicit read concern could skip orphan filtering on secondaries Created: 03/Mar/23 Updated: 29/Oct/23 Resolved: 12/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12 |
| Participants: |
| Description |
|
The ServiceEntryPoint relies on the presence of the "level" field in "readConcern" to check if shard versioning check is required on secondaries. |
| Comments |
| Comment by Githook User [ 12/Jun/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |