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

Ensure rename doesn't throw NamespaceNotFound once started

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2021-03-22

      Description

      Right now a concurrent drop might run concurrently with a rename, causing the command to fail with NamespaceNotFound. This behaviour is fine and expected, however, we could check if the NamespaceNotFound came from the first check done on the command specifically, by checking for the changelog collection.

        Attachments

          Activity

            People

            Assignee:
            pierlauro.sciarelli Pierlauro Sciarelli
            Reporter:
            marcos.grillo Marcos José Grillo Ramirez
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: