-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30, Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11
-
137
Currently, in stepUp while holding the RSTL, we recover the sharding state which includes making remote calls to the config server. This seems non-ideal and a liveness issue as we end up blocking while something has gone wrong with the config server.
- depends on
-
SERVER-60110 Get rid of ShardingStateRecovery once 7.0 branches out
- Closed
- is related to
-
SERVER-38409 Shard can crash at step-up due to FailedToSatisfyReadPreference exception during minOpTime recovery
- Closed
-
SERVER-56756 Primary cannot stepDown when experiencing disk failures
- Closed