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

enforce secondaryThrottle during moveChunk commit

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.7.8
    • None
    • Sharding
    • None
    • ALL

    Description

      The secondaryThrottle parameter is used during the bulk insert/remove operations of migrations, but is not used during commit - this is somewhat inconsistent if the secondaryThrottle write concern is stronger than the (necessary) majority-of-nodes-caught-up write concern used by the migration commit.

      By enforcing both majority-of-nodes and the specified secondaryThrottle, we should be as safe as before but also allow users to provide stronger migration commit guarantees.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: