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

moveChunk doesn't obey maxTimeMS consistently

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: 3.4.6, 3.5.10
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:
    • Operating System:
      ALL

      Description

      The moveChunk command crosses from mongos > config server > donor shard > recipient shard. Any maxTimeMS information gets lost after the config server.

      Currently it is not safe to always observe maxTimeMS or interrupt on the donor shard, because the migration critical section is not prepared to handle it and may result in fassert.

      This ticket is to figure out our story with moveChunk interruptability and deadline observance. Once it has been fixed, the disabled test below needs to be re-enabled.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: