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

dropIdent returning EBUSY during rollback_to_stable can crash server

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v8.0
    • Execution Team 2024-05-13
    • 135

      Failing to drop idents for an unfinished index build during recovery does not use the ident reaper and return any drop ident failure to higher level.

      As part of rollback to stable we re-open the catalog and restart unfinished index builds as needed. As we are in rollback to stable we're not able to modify the catalog (as we cannot perform timestamped writes) we'll reuse the ident name by dropping the previous ident and re-creating a new with the same name. Link.

      However, if dropping this ident fails, the status is returned and eventually converted to an exception here causing the catalog to not finish its setup as we throw here. This is completely unrecoverable and leads to further exceptions being thrown which terminates the process as we're already handling an existing exception (the failure to start the index build due to the failure to drop the ident)

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: