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

ShardRemote does not notify the ReplicaSetMonitor on write concern failures

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.10
    • 3.3.9
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 17 (07/15/16)

    Description

      The ShardRemote::_runCommand does not notify the replica set monitor for write concern errors, which causes the RSM to return the same host over and over again and never attempting to discover a new primary.

      This makes the auto-retry logic for config server commands not reliable and causes failures in the sharding continuous stepdown suite.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: