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

applyChunkOpsDeprecated should retry on notMaster or network errors

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.2.0-rc3
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding B (10/30/15), Sharding C (11/20/15)

    Description

      This was found through code inspection. The moveChunk command under CSRS will terminate the donor shard instance if the applyOps command returns a notMaster status. In particular, this line and the handling here.

      While we are at it, we should also get rid of the try/catch block around applyChunkOpsDeprecated because this method should never throw in 3.2.

      The splitChunk command will also benefit from the same retry logic.

      Attachments

        Activity

          People

            misha.tyulenev@mongodb.com Misha Tyulenev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: