[SERVER-80319] Test assumes replica set will be available in queryableBackupMode Created: 22/Aug/23  Updated: 29/Oct/23  Resolved: 23/Aug/23

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File repro.patch    
Issue Links:
Depends
Problem/Incident
is caused by SERVER-79046 The PreWriteFilter should be disabled... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Run the test with the attached repro applied.

Sprint: Sharding EMEA 2023-09-04
Participants:
Linked BF Score: 50

 Description   

SERVER-79046 added a new test to check the oplog application after startup in queryableBackupMode. This test is using a js helper to get a connection to the secondary node after it was restarted, this is wrong because internally we first try to determine a primary, and because we shutdown the node, the primary might relinquish being a primary, causing the getSecondary function call to hang indefinitely waiting for a primary that will never be elected, because when initialized with queryableBackupMode, a node cannot form part of a replica set.



 Comments   
Comment by Githook User [ 23/Aug/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-80319 Prevent checking for primary in replicaset which only secondary was restarted in queryableBackupMode node
Branch: master
https://github.com/mongodb/mongo/commit/02d4c605bb3b8df5e03eb9daf8b4174e04982aa7

Generated at Thu Feb 08 06:43:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.