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

MaxTimeMSExceeded on _configsvrMoveChunk can lead to blocking future migrations for that chunk

    XMLWordPrintable

    Details

    • Operating System:
      ALL

      Description

      If moveChunk is sent with maxTimeMS, the following scenario can occur:
      1. The config server sends moveChunk to the shard. The shard starts running it.
      2. The config server hits maxTimeMS, which then causes it to fail to delete the relevant config.migrations doc, which happens in the destructor of the object created here, since the OperationContext has been interrupted.

      If the config server gets another moveChunk attempt for that range, it will fail with DuplicateKeyError on config.migrations. config.migrations is keyed on namespace and the min value of the range being moved, so this will happen indefinitely for any chunk with the same min value.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: