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

startupRecoveryForRestore may not play nicely with collection drop applied during startup recovery

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.27, 5.0.24
    • Affects Version/s: 5.0.0, 4.4.7
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v5.0, v4.4
    • Execution Team 2023-11-13, Execution Team 2023-11-27

      On v5.0, when using recoverFromOplogAsStandalone, after recovering from the oplog we set the internal readOnly flag to true. If also using startupRecoveryForRestore, we have also advanced the oldest timestamp during the oplog application, as described in SERVER-55766. This means that the drop-pending ident reaper will run, dropping any tables from a collection drop applied during the recovery. Then when we go to drop the ident, we can run into an IllegalOperation error because the readOnly flag is set.

            gregory.noma@mongodb.com Gregory Noma
            gregory.noma@mongodb.com Gregory Noma
            0 Vote for this issue
            15 Start watching this issue