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

index creation on secondaries need not block readers

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Index Maintenance, Replication
    • None
    • Storage Execution

    Description

      On a secondary, a "foreground" (normal) index build could be done while still letting readers read. then we just swap in the index when it is ready with a very short write lock. that is, assuming here there are no other writers than the replication sync thread.

      while the index build is in progress i'm assuming other ops would not be applied, so some lag would accumulate, but it would be nice to still be readable. thoughts?

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25168 Foreground index build blocks all R/W on ALL database on a sharded cluster with secondaryPreferred read preference

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

          New Feature - A new feature of the product, which has yet to be developed. SERVER-6836 Allow index builds on secondaries with a "force" option.

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-2771 Background index builds on replica set secondaries

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-18301 Allow reads during foreground index builds

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-20328 Allow secondary reads while applying oplog entries

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

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              dwight@mongodb.com Dwight Merriman
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: