[SERVER-61847] Handle direct updates/deletes to shards that modify orphan docs Created: 02/Dec/21  Updated: 29/Oct/23  Resolved: 27/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-58036 TTL monitor can delete documents duri... Closed
Problem/Incident
causes SERVER-63245 TTL Monitor thread doesn't recover th... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07
Participants:
Linked BF Score: 135

 Description   

The goal of this task is to explore how to handle direct updates/deletes to shards that modify orphan documents.  The initial proposal is to mark the oplog associated to these ops with the fromMigrate flag, so the current infrastructure of changestream should be already able to filter them out.



 Comments   
Comment by Githook User [ 27/Jan/22 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-61847 Handling direct update/removes to shards
Branch: master
https://github.com/mongodb/mongo/commit/023d9930f82a0ba85cd965793626d36baad52ad8

Generated at Thu Feb 08 05:53:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.