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

secondary_reads_waitForShardingInit.js does not force mongos choose the right shard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • 35

    Description

      in secondary_reads_waitForShardingInit.js, we expect the mongos always send the request to the hanging secondary node. But, the test code does not force mongos to choose the shard which has that node. If mongos send request to another shard, the test will fail. BF-24464 hit this error case. 

      To fix it, we should force the mongos choose the right shard.

      Also, in this js file, the way of using session should be improved too. 

      Attachments

        Activity

          People

            sophia.tan@mongodb.com Sophia Tan
            sophia.tan@mongodb.com Sophia Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: