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

Applying dropIndexes oplog entry can get BackgroundOperationInProgressForNamespace if FCV not upgraded

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0, 5.2.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.2
    • Execution Team 2022-01-10
    • 155

      SERVER-49866 added an invariant that if we get BackgroundOperationInProgressForNamespace applying an oplog entry, the node must be in initial sync. After SERVER-59399 this is true since we no longer assert that there are no index builds in progress on a collection in order to drop a different index on that collection. However, if the FCV is not upgraded, we actually still throw this assertion. Thus, if the FCV is not fully upgraded, attempting to apply a dropIndexes oplog entry in steady state replication can result in BackgroundOperationInProgressForNamespace if there is an active index build in progress on that collection.

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