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

Make rsm_horizon_change.js unknown server description test resilient to RSM state transition

    XMLWordPrintable

Details

    • Minor Change
    • ALL
    • Hide

      Difficult to reproduce

      Show
      Difficult to reproduce
    • Sharding NYC 2022-04-04
    • 16
    • 2

    Description

      The rsm_horizon_change.js tests that the split horizon reconfig causes the ReplicaSet to go into RSNoPrimary before going back into RSPrimary State.

      Fixed a few months ago, SERVER-57893, explains how due to network events it can lead the Topology Change to the following states before going into RSPrimary State

      1. RSNoPrimary or
      2. It can send RSM into "RSM monitoring host in expedited mode until we detect a primary". 

      But the latest error shows that drop in connections can also lead RSM monitor to stay in RSPrimaryState(by dropping connections in reconfig state and then reconnecting)

      Suggested Fix: Add additional log check for "Dropping all pooled connections" to 
      unknownServerDescriptionRegex

      Attachments

        Issue Links

          Activity

            People

              rachita.dhawan@mongodb.com Rachita Dhawan
              rachita.dhawan@mongodb.com Rachita Dhawan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: