Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65745

Discrepancy in the result returned by isRetryableError() when input is command response error code vs error message.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Service Arch
    • ALL

      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"

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: