[SERVER-50909] Only apply changed connection strings inside ShardRegistry::_lookup() Created: 14/Sep/20 Updated: 29/Oct/23 Resolved: 06/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Jaume Moragues (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
The code inside ShardRegistry::_lookup() blindly applies the latest connection string for each shard to the ShardRegistryData being generated. Most of the time, these connection strings will be the same as what's already in the ShardRegistryData, meaning that the work of integrating them is unnecessary. It should be possible to short-circuit (continue) prior to this work, if the returnData ShardRegistryData already associates this connection string with the correct shard. |
| Comments |
| Comment by Githook User [ 05/Nov/20 ] |
|
Author: {'name': 'Jaume Moragues', 'email': 'jaume.moragues@mongodb.com'}Message: |