[SERVER-56595] Create collection coordinator could fetch stale coll info from CSRS Created: 04/May/21  Updated: 29/Oct/23  Resolved: 12/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56555 Enable drop_collection_sharded.js FSM... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Currently the create collection coordinator retrieves collection information through the catalog cache that in turn relies on the sharding catalog client to retrieve this data. Since the catalog cache uses a combination of nearest read preference and snapshot read concern it could read stale data from a secondary node of the CSRS. If this happen the create collection coordinator would wrongly assume that the collection has not been committed yet.



 Comments   
Comment by Githook User [ 12/May/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-56595 Add function to serialize cache refreshes after writes on the config server

Co-authored-by: Marcos José Grillo Ramirez <marcos.grillo@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/7b9eb05ea26dd0adba9c097ba1fe68dc3c2e1ba1

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