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

Command application conflicting with index build should wait for its completion (partial revert of SERVER-61481)

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Execution Team 2023-05-15
    • 7

      SERVER-74953 describes a situation where a stepdown occurs while an index build is in its early setup phase, immediately followed by a DDL operation that conflicts with the index build, like dropCollection. The now-secondary mongod attempts to replicate the dropCollection. Before SERVER-61481, replication would have detected the conflict and would have waited until no index build was in progress before retrying the operation. SERVER-61481 removed that logic, and since then this results in an invariant failure.

      Note that this issue is very infrequent and results in one (and just one) secondary crash. Upon restart, the secondary is able to resume replication.

      This ticket is to reintroduce part of the logic that was removed in SERVER-61481.

            Assignee:
            josef.ahmad@mongodb.com Josef Ahmad
            Reporter:
            josef.ahmad@mongodb.com Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: