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

Retry on network errors for commands run through the add shard task executor

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • 28

    Description

      When adding a new shard, the config server sends several requests to the shard using a separate task executor, likeĀ isMaster, listDatabases, and a drop of the sessions collection. These requests are not retried on network errors, or any retryable errors, unlike commands run through the Shard interface.

      It looks like prior to 3.4, a different code path was used for these requests, that did retry on retryable errors.

      Attachments

        Activity

          People

            mira.carey@mongodb.com Mira Carey
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: