[SERVER-71621] Define new oplog entry types to match the commit of existing Sharding DDL operations Created: 25/Nov/22 Updated: 29/Oct/23 Resolved: 12/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| 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: | Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23 | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
In order to maintain an optimal set of open connections while serving an nss/cluster.watch() request, mongos must be notified of any event that modifies the current data placement of the nss/cluster being targeted through the emission of an oplog event. As per today, the following Sharding DDL operations do not emit any information when committed:
The objective of this ticket is defining a new oplog entry type for each aforementioned command. (Separate tickets will be created to also implement the logic to emit them). |
| Comments |
| Comment by Githook User [ 12/Jan/23 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |