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

Add reshardingCriticalSectionTimeoutMillis server parameter

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None

    Description

      Add a server parameter for an upper limit on how long to wait to hear back from recipient shards reaching strict consistency after engaging the critical section. This is to bound the amount of write unavailability in case the estimated time remaining turns out to be inaccurate. Default value isn’t decided but should be around 5-10 seconds

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              lamont.nelson@mongodb.com Lamont Nelson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: