[SERVER-68700] config.shards not updated on reconfig in catalogShard POC Created: 09/Aug/22  Updated: 04/Oct/22  Resolved: 04/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Duplicate Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-68749 Need to persist the catalogShard fiel... Closed
Sprint: Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19, Sharding 2022-10-03, Sharding 2022-10-17
Participants:
Story Points: 3

 Description   

Apparently reconfig command removing a server from catalogShard doesn't update the config.shards.
Repro jstests/sharding/mongos_no_replica_set_refresh.js

The half of the root cause is that the updateReplicaSetOnConfigServer() method is skipping changing the config.shards on the config server because the config server is doing it by itself. The fix will be find where on the config this is supposed to happen and adjust it for the catalog shard behavior.


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