renameCollection should handle WriteConflictException

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • ALL
    • Quint Iteration 3, Quint Iteration 4, Quint Iteration 5, Storage NYC 2019-05-06
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Like SERVER-17061, this command should be robust to WriteConflictException. Unlike the commands in SERVER-17061, these commands depend at least on SERVER-17062, which makes query execution robust to WriteConflictException.

      This ticket as split off of SERVER-17075, as the renameCollection is more involved and quite separate from cloneCollectionAsCapped.

              Assignee:
              Geert Bosch
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: