[SERVER-73271] Fix deadlock when the config server coordinator contacts itself as a shard Created: 24/Jan/23  Updated: 29/Oct/23  Resolved: 26/Jan/23

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

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

Backwards Compatibility: Fully Compatible
Participants:

 Description   

When the catalog shard handles the setFeatureCompatabilityVersion command (via the run() member function in the SetFeatureCompatibilityVersionCommand class) it acquires a lock and eventually sends a setFeatureCompatabilityVersion command to all the shards. Since the catalog shard is also a shard, it will handle the command and attempt to acquire a lock again resulting in a deadlock.



 Comments   
Comment by Githook User [ 25/Jan/23 ]

Author:

{'name': 'wenqinYe', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-73271 Fix deadlock when the config server coordinator contacts itself as a shard
Branch: master
https://github.com/mongodb/mongo/commit/b4258ca56086b52db1dafcd43c87d28711ce0d5b

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