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

Race between isMaster response connection hook and RSM topology change triggers ShardNotFound

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 4.4.0-rc0, 4.3.5, 4.3.6, 4.4.0-rc10
    • Sharding
    • ALL
    • 35

    Description

      On the reception of a isMaster response the RSM installs the new server description and possibly changes the topology type for the corespondent replica set. The same isMaster response will also trigger a NetworkConnectionHook::vlidateHost() that will try to do a reverse lookup host->shard that will fail triggering a ShardNotFound error.

      Attachments

        Activity

          People

            lamont.nelson@mongodb.com Lamont Nelson
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: