[SERVER-65745] Discrepancy in the result returned by isRetryableError() when input is command response error code vs error message. Created: 18/Apr/22  Updated: 17/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: neweng, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Operating System: ALL
Participants:

 Description   

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"


Generated at Thu Feb 08 06:03:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.