-
Type: Bug
-
Resolution: Declined
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
-
v6.0, v5.0
-
Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27
SERVER-66658 intended to solve a race between two different threads trying to access the shard registry while it was being refreshed, however, now we might return that the shard registry is up when it isn't, because comparing the shard registry time with Time() will always be false due to the forceReloadIncrement component.
We should get the topology version component and only compare that with Timestamp() instead.
- is caused by
-
SERVER-66658 Shard registry might be accessed before initialization
- Closed