[SERVER-53034] Investigate internal usages of "isMaster" in sharding Created: 23/Nov/20  Updated: 09/Aug/23  Resolved: 09/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Silvia Surroca
Resolution: Duplicate Votes: 0
Labels: sharding-common-backlog, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-77154 Change server's internal client imple... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21
Participants:

 Description   

Based on the comments in sharding_catalog_manager_shard_operations.cpp, addShard validates the host as a shard and calls "isMaster". Since we added the new hello command, we should evaluate whether or not we can change internal isMaster calls or if we need to rely on them to communicate with older versions of the server.

Related files:
sharding_network_connection_hook*
sharding_catalog_manager_add_shard_test
sharding_connection_hook*


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