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

Initial sync failure must abort all in-progress index builds before restarting

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc9, 4.7.0
    • Storage
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-06-15
    • 8

    Description

      There is a test failure where:

      The codepath for hitting the invariant is coming through:

      • InitialSyncer::_truncateOplogAndDropReplicatedDatabases
      • StorageInterfaceImpl::dropReplicatedDatabases
      • DatabaseHolderImpl::dropDb
      • invariantFailedWithMsg

      DatabaseHolderImpl::dropDb technically expects the caller to have checked for in-progress index builds before calling, which didn't happen. I suppose initial sync finding an index build in-progress at a higher level is also an invariant'ing offense. Maybe think about it a bit more whether some higher level invariant about no index builds in progress should be added, or not.

      Attachments

        Activity

          People

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            dianna.hohensee@mongodb.com Dianna Hohensee
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: