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

race in multi_mongos2.js can cause count to be targetted to wrong shard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • 3.5.13
    • Sharding
    • ALL
    • Sharding 2019-12-02
    • 0

    Description

      Setup: 2 mongos, 2 shards.

      1. movePrimary sent to mongos1.
      2. movePrimary changed primary from shardA to shardB
      3. send insert to mongos1.
      4. send count to mongos2. Mongos2 still sees state before movePrimary and routes count to shardA.
      5. shard does not reject count since version matches (0,0|0) matches (0,0|0)
      6. counts shows 0 documents.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: