-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
isRetryableError() now accepts error code and error message input types. Input of type error messages iterate through hard-coded list of retryable errors maintained on js side to figure out if the error is an retryable error, whereas for error code(/ command response) input type, it iterates through list of error codes that’s tagged as retryable via error_codes.yml. And, those 2 lists are completely different.
Example conflicting error codes: "Interrupted", "MaxTimeMSExpired", "BackupCursorOpenConflictWithCheckpoint", "ConnectionPoolExpired"
- is related to
-
SERVER-105930 isRetryableError in utils.js is unreliable
-
- Backlog
-