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

Capture NetworkInterfaceExceededTimeLimit and MaxTimeMSExpired errors in resharding participants

    • Fully Compatible
    • ALL
    • v5.0
    • Sharding 2021-07-26, Sharding 2021-08-09
    • 1

      In resharding, shards call into the config server in order to update the coordinator document (donor, recipient). NetworkInterfaceExceededTimeLimit and MaxTimeMSExpired errors are not considered retriable, but are definitely reachable – these commands have a timeout of 30 seconds, and one of the listed errors will be thrown if the timeout is reached. These errors will escape any command retrying and resharding-specific transient error retrying, and will ultimately cause an fassert on whatever node is running resharding.

      The solution here is to figure out the best place to swallow and retry these errors.

            matt.walak@mongodb.com Matthew Walak (Inactive)
            blake.oler@mongodb.com Blake Oler
            0 Vote for this issue
            3 Start watching this issue