[SERVER-74667] Use lock-free read approch for checkMetadataConsistency command Created: 07/Mar/23  Updated: 29/Oct/23  Resolved: 16/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-75021 Coverity analysis defect 135525: Dere... Closed
Related
related to SERVER-75285 Deadlock between ShardsvrCheckMetadat... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 135

 Description   

Explore possible usage of lock-free read in the checkMetadataConsistency participant command probably somenthing similar to what list_collections does



 Comments   
Comment by Githook User [ 16/Mar/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-74667 Use lock-free read approch for checkMetadataConsistency command
Branch: master
https://github.com/mongodb/mongo/commit/1ca7dd4d7a4f2a9bbe8f9d8ad8a8442b91c3baad

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