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

Investigate whether recvChunkStart command should have a timeout

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability

      In HELP-57694, a customer attempted to kill a chunk migration by interrupting the _recvChunkStart command. This didn't actually kill the migration, but it did bring to light that the migration was stuck due to the _recvChunkStart command waiting for a write concern that it couldn't fulfil (in this case, the write concern was set to w: 3 and only 2 nodes were up).

      The purpose of this ticket is to investigate whether there should be some timeout attached to the _recvChunkStart command to prevent this.

            Assignee:
            Unassigned Unassigned
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: