Reads during concurrent rename may call openCollection with the wrong namespace when reading using UUID

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2023-02-20, Execution Team 2023-02-06
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We resolve the UUID to a NamespaceString that is then used for the rest of the read setup.

      However, when there is a concurrent rename that is committed to the storage engine but not to the in-memory catalog we wrongly report this as the collection not existing.

      We need to perform openCollection with a UUID in this case to be correct.

              Assignee:
              Henrik Edin
              Reporter:
              Henrik Edin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: