[SERVER-51342] ShardRegistry should forget connection strings of removed shards Created: 04/Oct/20  Updated: 29/Oct/23  Resolved: 11/Oct/20

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-51450 Use new $currentOp aggregation pipeli... Closed
Related
related to SERVER-51257 ShardRegistry should properly handle ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 11/Oct/20 ]

Author:

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

Message: SERVER-51342 ShardRegistry should forget connection strings of removed shards
Branch: master
https://github.com/mongodb/mongo/commit/bd1f707b4e981aeea09d3a0e0774973b9c223eb2

Comment by Tommaso Tocci [ 09/Oct/20 ]

These changes are making the count10.js test to fail because the currentOp output get truncated and the match filter can't be applied, thus SERVER-51450 became a prerequisite for this to be committed.

Generated at Thu Feb 08 05:25:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.