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

Unify NamespaceNotFound handling when calling applyOperation_inlock

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Replication
    • Labels:

      Description

      applyOperation_inlock() needs the collection lock held before calling the function, which may throw a NamespaceNotFound error. As a result, all callers have to handle NamespaceNotFound correctly for idempotency reasons. We should unify the logic.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: