[SERVER-44498] Create a flag on the OperationContext to indicate that an operation needs to block on a collection refresh. Created: 08/Nov/19  Updated: 29/Oct/23  Resolved: 30/Dec/19

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

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

Issue Links:
Gantt Dependency
has to be done before SERVER-44500 Create a new ShardVersionMap that inc... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13
Participants:

 Description   

Feature Work

Create a flag on the OperationContext that indicates if an operation needs to block behind the next catalog cache refresh. Set this flag to always be true, as our initial state. Create the logic that would return the chunk distribution even if it’s marked as needsRefresh if the flag is set to false. Behavior should be maintained, since the flag is always set to true as of the completion of this ticket.

Testing Work

Create unit tests to verify the interaction between needsRefresh and and the new OperationContext flag.



 Comments   
Comment by Githook User [ 30/Dec/19 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-44498 Create an OperationContext flag to indicate that an operation can skip a catalog cache refresh
Branch: master
https://github.com/mongodb/mongo/commit/270069526e8e6f1b2ba2c1cc87f38ff750a8cb60

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