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

moveChunk doesn't obey maxTimeMS consistently

XMLWordPrintableJSON

    • Sharding EMEA
    • ALL

      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.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: