-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.0.1
-
Component/s: Testing Infrastructure
-
Server Tooling & Methods
-
ALL
-
22
The error code for exceeding timeouts was determined to be ambiguous and was changed in SERVER-35031. We should update places that expect these errors in resmoke to handle the new error code. Right now the only place is in the stepdown hook.
Note that there has been no change in pymongo throughout this process; it doesn't know about the new error code for ExceededTimeLimit and treats it as a generic OperationFailure. So the error handling code in stepdown.py should be changed to handle OperationFailure as well.
We should also check that the code for the OperationFailure is indeed for ExceededTimeLimit(262) and still bubble up other errors.
Affects master and 4.0 branches for now, but based on comments in SERVER-35031, it will be backported to earlier branches later.
- is related to
-
SERVER-36817 replSetFreeze command run by stepdown thread may fail when server is already primary
- Closed
-
SERVER-35031 ExceededTimeLimit (50) is reported in situations unrelated to maxTimeMS
- Closed