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

Enforce reshardingCriticalSectionTimeout parameter

    XMLWordPrintable

Details

    • Fully Compatible
    • Sharding 2021-04-05
    • 62
    • 2

    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.
      • Should abort the resharding operation if the timeout is reached before reaching strict consistency after engaging the critical section.

      Attachments

        Issue Links

          Activity

            People

              kshitij.gupta@mongodb.com Kshitij Gupta
              lamont.nelson@mongodb.com Lamont Nelson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: