[SERVER-62315] Cache the sharding ownership filter in the update/delete stage Created: 30/Dec/21  Updated: 29/Oct/23  Resolved: 21/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.3.0
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
Problem/Incident
Related
related to SERVER-62279 Micro-optimize the skipWriteToOrphanD... Closed
is related to SERVER-61767 Optimizing the new way of filtering w... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07
Participants:
Linked BF Score: 135

 Description   

SERVER-59832 introduced a few changes to skip update/delete operations over orphan documents. In order to know if an operation affects an orphan document, we need the sharding ownership filter. The current implementation is asking for the ownership filter for each document but we know that if the collection lock is not yield it's going to be the same.

The goal of this task is to cache the ownership filter and only refresh it when we recover the lock (i.e. after a yield).



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

Author:

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

Message: SERVER-62315 Cache the ownership filter on the update/delete stage
Branch: master
https://github.com/mongodb/mongo/commit/3c8e968f2d7da85d62d3381bec6b308d2be830d8

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