-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Sharding NYC
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The current code for PM-3190 only deals with StaleConfig errors arising out of stale config metadata. It is also possible to receive a StaleDBVersion error if a movePrimary command is run in between the execution of a large batch of writes. We should kick in the retry protocol for broadcast if we encounter such an error when attempting updateOne or deleteOne relevant to this project.