Clarify expected error if backoff exceeds CSOT's deadline in withTransaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: CSOT, Transactions
    • None
    • Hide

      DRIVERS-3391:
      Summary of necessary driver changes

      • Clarify that when withTransaction retry backoff and jitter would exceed a client-side timeout—either the legacy withTransaction retry time limit or, if CSOT is in use, the CSOT deadline—drivers must raise a timeout error derived from the original error, wrapping that error as the cause, instead of rethrowing the raw error directly.

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

       

      Show
      DRIVERS-3391 : Summary of necessary driver changes Clarify that when withTransaction retry backoff and jitter would exceed a client-side timeout—either the legacy withTransaction retry time limit or, if CSOT is in use, the CSOT deadline—drivers must raise a timeout error derived from the original error, wrapping that error as the cause, instead of rethrowing the raw error directly. Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) https://github.com/mongodb/specifications/commit/e83452055d60b27bc943900504ba926bea57690e    
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3391, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: