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

renameCollection should handle WriteConflictException

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Quint Iteration 3, Quint Iteration 4, Quint Iteration 5, Storage NYC 2019-05-06

      Description

      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.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31022 renameCollection with dropTarget can segfault on 3.5

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

            Activity

              People

              Assignee:
              geert.bosch Geert Bosch
              Reporter:
              geert.bosch Geert Bosch
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: