[SERVER-62881] Make rsm_horizon_change.js unknown server description test resilient to RSM state transition Created: 21/Jan/22  Updated: 29/Oct/23  Resolved: 29/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Rachita Dhawan Assignee: Rachita Dhawan
Resolution: Fixed Votes: 0
Labels: neweng, sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2022-01-21-15-02-04-805.png    
Issue Links:
Depends
Related
related to SERVER-57893 Make rsm_horizon_change.js resilient ... Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Steps To Reproduce:

Difficult to reproduce

Sprint: Sharding NYC 2022-04-04
Participants:
Case:
Linked BF Score: 16
Story Points: 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



 Comments   
Comment by Githook User [ 28/Mar/22 ]

Author:

{'name': 'Rachita Dhawan', 'email': 'rachita.dhawan@gmail.com', 'username': 'racdhawan'}

Message: SERVER-62881: Add dropping pooled connection regex
Branch: master
https://github.com/mongodb/mongo/commit/e6bae62861fbc97245fadd2efff98e2fc15ab250

Generated at Thu Feb 08 05:56:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.