Avoid using streamable RSM in max_time_ms_sharded.js due to maxTimeAlwaysTimeOut failpoint

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • 31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The streamable RSM includes a maxAwaitTimeMS in its hello request and the maxTimeAlwaysTimeOut failpoint causes the hello request to immediately hits its deadline. This leads the mongos to not know the replica set member state of the shards.

            Assignee:
            Max Hirschhorn
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: