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

Clear drop pending reaper state before re-opening the catalog after rollback to stable

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Execution Team 2023-06-12
    • 151

      Right now we clear the drop pending state after rollback to stable, and re-opening the catalog. During re-opening, we can register internal idents that need to be dropped. But if the internal ident is already registered, we'll hit a fatal assertion. So we need to flip the ordering.

      What's worse, with the current ordering, is that catalog re-opening can register internal idents to drop, but we clear the state shortly after. These idents would not be dropped until a server restart.

       

       

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: