[SERVER-77554] defer oplog reservation in collection_internal::deleteDocument() Created: 30/May/23 Updated: 29/Oct/23 Resolved: 01/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2023-06-12 | ||||||||
| Participants: | |||||||||
| Description |
|
In the delete code path, we currently reserve oplog slots for retryable findAndModify, which takes up replication resources, before calling OpObserver::aboutToDelete(), which does not really require the oplog resources and needs to notify numerous OpObserver implementations before completing. The oplog slots are needed for OpObserver::onDelete() to write the oplog entries so it would be beneficial to defer reserving the oplog slots until aboutToDelete() returnes. |
| Comments |
| Comment by Githook User [ 31/May/23 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |