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

enforce secondaryThrottle during moveChunk commit

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.8
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      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

          Issue Links

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: