-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
Currently the entry for a shard in _latestConnStrings isn't removed when that shard is removed from the cluster. This is harmless in the sense that it will be skipped and not used, but it needlessly wastes memory, and could cause problems if a shard is later re-added with the same replica set name as the removed shard was using. Therefore this entry should be removed when the ShardRegistry notices that the shard has been removed from the cluster.
- depends on
-
SERVER-51450 Use new $currentOp aggregation pipeline stage in count10.js
- Closed
- related to
-
SERVER-51257 ShardRegistry should properly handle "possible" RSM updates for the config shard
- Closed