-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Execution Team 2019-11-04
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
dbHash can throw a WriteConflict error for the same reason described in SERVER-43066 at _getNextImpl as part of _hashCollection. And dbHash also uses PlanExecutor::NO_YIELD, which makes it more likely.
This is a problem for the dbHash background hook. And I think it is reasonable to fix this at the command-level to make it more resilient to errors.
- related to
-
SERVER-43060 CheckReplDBHashInBackground should retry the "dbHash" command on WriteConflicts
-
- Closed
-