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

Evaluate locations that throw WriteConflictExceptions without a real write conflict

    XMLWordPrintableJSON

Details

    • Task
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • Storage Execution NAMER

    Description

      We sometimes use write conflict exceptions for events that are actually unrelated to write conflicts (example). Audit these locations and determine whether they warrant a using a different error code and handling policy (e.g. TemporarilyUnavailable).

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-77542 Internal operations should handle TemporarilyUnavailable and TransactionTooLargeForCache exceptions

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-60839 Introduce a TemporarilyUnavailable error type

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-execution-namer@mongodb.com Backlog - Storage Execution NAMER
              josef.ahmad@mongodb.com Josef Ahmad
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: