-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
In SERVER-61003 we added a logic on the ShardRegistry reload function to retry ReadConcernMajorityNotAvailableYet error coming from the CSRS.
Retrying this error shouldn't be necessary at all since this errors could only happen during initialization of the ShardRegistry and before the sharding state is marked as initialized.
- is related to
-
SERVER-61003 ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
- Closed