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

Allow enforcement of additional custom write concern at pre-commit

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Sharding
    • None
    • Sharding

    Description

      The write concern of secondaryThrottle can be fine tuned (SERVER-14041), and is applied at pre-commit (as well as the normal w:majority WC) in case it's stronger than w:majority (or uses tags to target certain nodes) (SERVER-15591). However, a valid use case is a stronger/more targeted WC at pre-commit, but without slowing down the whole migration (as using secondaryThrottle would).

      This request is to allow a custom pre-commit write concern to be configured and applied (in addition to w:majority), i.e. similar to SERVER-14041/SERVER-15591 except only at the end of the migration, not the whole way through (which is what secondaryThrottle is). (wtimeout should not be supported at pre-commit, since it would always be pointlessly unsafe.)

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              kevin.pulo@mongodb.com Kevin Pulo
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: