[SERVER-37052] Add missing check for ReplicaSetMonitor error in JS retryable writes override Created: 07/Sep/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: tig-bfday-eligible
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Assigned Teams:
Server Tooling & Methods
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Participants:
Linked BF Score: 15
Story Points: 2

 Description   

The replica set monitor can throw two types of errors (1, 2) when no master is visible. The retryable writes JS override should check for both types of errors.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Max Hirschhorn [ 13/Sep/18 ]

We can potentially check for the "can't connect to new replica set master" error message coming back from DBClientReplicaSet based on its location code instead of using another regular expression. We may not want to switch the case we're currently handling to be based on FailedToSatisfyReadPreference because we'd lose information that the read preference is mode="primary".

Generated at Thu Feb 08 04:44:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.