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

Retry `moveChunk` indefinitely when router hits retriable errors

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc8, 6.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-06-13
    • 163

    Description

      Before v6.0, moveChunk operations issued by users where ending up calling into the configsvr_client that was issuing runCommand with idempotent retry policy, resulting in indefinitely retrying the command in case of retriable errors.

      With the introduction of the moveRange path, the semantic has been involuntarily changed to a retry with fixed retry attempts both for moveRange and for moveChunk.

      Purpose of this ticket is to reintroduce the original retry logic.

       

      Attachments

        Activity

          People

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: