[SERVER-74168] Attempting to add the config server as a shard shouldn't remove its RSM Created: 17/Feb/23  Updated: 29/Oct/23  Resolved: 02/Mar/23

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

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

Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2023-03-06
Participants:

 Description   

As of SERVER-73685 the way to make the config server a catalog shard is to run the transitionToCatalogShard command. A user can still attempt to add the config server as a shard via addShard, which is correctly rejected, but will trigger removing the ReplicaSetMonitor for the config server via this scope guard, which should not happen because the config server still needs to be able to target itself.

We should also investigate if addShard/transitionToCatalogShard is creating a new RSM for the config server when it creates a Shard object here. The config server will always already have an RSM for itself, so this would be unnecessary.



 Comments   
Comment by Githook User [ 27/Feb/23 ]

Author:

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

Message: SERVER-74168: Attempting to add the config server as a shard shouldn't remove its RSM
Branch: master
https://github.com/mongodb/mongo/commit/45782b523d65366a94e5366c2e95f9322cf56385

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