[SERVER-67281] provide OpObserver hooks for starting batched writes Created: 14/Jun/22 Updated: 29/Oct/23 Resolved: 29/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-06-27, Execution Team 2022-07-11 |
| Participants: |
| Description |
|
The WriteUnitOfWork commits batched writes (multiple CRUD ops to replicate together within a single applyOps oplog entry) through an OpObserver event. However, we start batched writes by instantiating the decorator within the WriteUnitOfWork's constructor. It would be more consistent to extend the OpObserver interface to include methods for starting and aborting batched writes. This would also remove the need for the WriteUnitOfWork class to depend on the BatchedWriterContext. |
| Comments |
| Comment by Githook User [ 29/Jun/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 28/Jun/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 28/Jun/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 28/Jun/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |