-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.0, 4.9.0
-
Component/s: None
-
Fully Compatible
-
ALL
-
v5.0
-
-
Sharding EMEA 2021-05-31
-
170
When setFCV(v4.4) overlaps with a ShardRegistry reload - right after the useActualTopologyTime check - the ShardRegistry can fall into an infinite loop of lookups because the topology time is not gossiped after the setFCV succeeds.
Purpose of this ticket is to avoid this overlap to result in a livelock.
- is depended on by
-
SERVER-57017 Enable sharded DDL plus FCV FSM in stepdown suites
- Closed