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

mongos will not retry configsvrShardCollection when it gets a not master error calling listIndexes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.1.1
    • Component/s: Sharding
    • None
    • Sharding
    • ALL

      This is because configsvrShardCollection uses ScopedDBConnection to send the listIndexes command. When it gets a NotMaster error, it will convert it into it's own error code here. And this makes the error "non-retryable" since the custom error code is not in the list of retryable errors.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: