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

Background index builds for RTT on startup replication recovery corrupt _mdb_catalog

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Repl 2018-04-09
    • 21

    Description

      The LogicalClock is not initialized when performing replication recovery at startup. Completing a background secondary[1] index must set a legal timestamp. However the predicate to assign a timestamp fails because `startup` is not guaranteed to have a valid logical clock state.

      [1] It's perhaps unclear why I call the index build a background secondary index build. The index build is kicked off by an oplog entry and as such intersects much of the same code path as a typical secondary index build.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30939 Multiple index builds on same collection can livelock on WriteConflictExceptions

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-43097 Improve log messaging when index builds get foregrounded because of startup recovery

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30939 Multiple index builds on same collection can livelock on WriteConflictExceptions

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              daniel.gottlieb@mongodb.com Daniel Gottlieb
              daniel.gottlieb@mongodb.com Daniel Gottlieb
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: