[SERVER-62128] Do not assume FCV stability while filtering orphan documents in update/delete ops Created: 17/Dec/21  Updated: 29/Oct/23  Resolved: 28/Dec/21

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
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-12-27
Participants:
Linked BF Score: 152

 Description   

This issue was introduced in  SERVER-59832.

The changes introduced in that commit assume that we have FCV stability during the execution of an update operation. However that's not true:  it could totally happen that we decide at this point that we are going to filter writes over orphan documents, but then when we re-evaluate the value of the feature flag in the getOwnershipFilter function we see that the feature flag isn't enabled anymore and hit the invariant.



 Comments   
Comment by Githook User [ 28/Dec/21 ]

Author:

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

Message: SERVER-62128 Do not assume FCV stability when filtering writes
Branch: master
https://github.com/mongodb/mongo/commit/0465077ab52fbc4683b2633fec53b2153293bb07

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