-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding 2020-10-19
-
14
In SERVER-47169, the solution to a class of problem was to have the RSM call ShardRegistry::updateReplSetHosts() synchronously. However, SERVER-46202 changed the ShardRegistry behaviour such that updateReplSetHosts() no longer incorporates these updates synchronously. Instead, they are incorporated in the next ShardRegistry refresh, which is scheduled asynchronously. In order to avoid reintroducing the problem solved by SERVER-47169, updateReplSetHosts() should wait for this refresh to complete.
- related to
-
SERVER-47169 Sharding initialization contacts config shard before ShardRegistry updated by RSM, preventing mongos from starting up
- Closed
-
SERVER-46202 Implement ShardRegistry on top of ReadThroughCache to make it causally consistent
- Closed