[SERVER-67352] Skip identifying writes on orphaned documents in replica set deployments Created: 17/Jun/22 Updated: 29/Oct/23 Resolved: 22/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc11, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||||||
| Sprint: | Sharding EMEA 2022-06-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 135 | ||||||||||||||||
| Description |
|
In case of a client directly connected to a shard of sharded deployment, write operations on orphaned documents are properly flagged in order to avoid notifications on change streams (see PM-2423). The logic to identify if a write operation involves an orphaned document is relatively expensive, and it's currently triggered in replica set deployments as well. This is useless and wasteful as there are no orphaned documents. The goal of this ticket is to review where the currently logic is used (e.g., here) and restrict it to nodes that are part of a sharded deployments. |
| Comments |
| Comment by Githook User [ 23/Jun/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Githook User [ 23/Jun/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Githook User [ 22/Jun/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |