[SERVER-81019] Make dbCheck apply in parallel with CRUD operations on secondaries Created: 13/Sep/23 Updated: 30/Nov/23 Resolved: 30/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Moustafa Maher |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-855-milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2023-11-27, Repl 2023-12-11 |
| Participants: |
| Description |
|
During oplog application, dbCheck current is applied in its own batch. As an optimization, it should instead be applied alongside other CRUD operations within a batch, as it is a read-only operation. We will need to make sure that the readTimestamp the batch is reading at is already available on the secondary. |
| Comments |
| Comment by Githook User [ 30/Nov/23 ] |
|
Author: {'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: |