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

Catch FailedToSatisfyReadPreference in DDL fsm workloads

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • 5.1.0, 5.0.2
    • None
    • Sharding
    • ALL
    • v5.0
    • Sharding EMEA 2021-09-06
    • 144

    Description

      If the RSM on any node times out while trying to discover a new primary host, we could throw FailedToSatisfyReadPreference. We should account for that error in this test.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-60706 Retry FailedToSatisfyReadPreference errors while performing retryable writes

          • Major - P3 - Major loss of function.
          • Backlog
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59409 Race between reconfig replication and stepup can cause RSM to be stuck in reporting ReplicaSetNoPrimary

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              jason.zhang@mongodb.com Jason Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: