[SERVER-63546] Investigate the difference in RSM handling of Config and shard servers Created: 10/Feb/22  Updated: 29/Oct/23  Resolved: 21/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Kshitij Gupta
Resolution: Fixed 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
is depended on by SERVER-63598 Umbrella ticket for minimal POC for o... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-03-07, Sharding NYC 2022-03-21
Participants:
Story Points: 3

 Description   

The Hello reply payload is slightly different in Config and shard servers. Moreover, RSM expects to receive two separate replies from Config and shard servers. If we keep RSM to not know that the Config and shard servers merged it may conflict on host:port be the same for two servers. If we make the combined server to reply only once the internal SDAM protocol may require a non-compatible change.

We can also chose to keep the Config and shard servers on different ports to effectively separate them for the external observer. This will require to also create separate transports for them.


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