[SERVER-61665] Ensure read is directed to hanging secondary node in secondary_reads_waitForShardingInit.js Created: 19/Nov/21  Updated: 29/Oct/23  Resolved: 24/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Bug Priority: Major - P3
Reporter: Sophia Tan Assignee: Sophia Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 36

 Description   

In secondary_reads_waitForShardingInit.js, we should ensure read is directed to hanging secondary node instead of any other secondary node. 

Currently, we do it by hiding another secondary node by reconfiguring the replica set. But, we did not wait for the node becoming hidden. So, the secondary preference read still get chance to be directed to another secondary node instead of the hanging secondary node.



 Comments   
Comment by Githook User [ 23/Nov/21 ]

Author:

{'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}

Message: SERVER-61665 Ensure read is directed to hanging secondary node in secondary_reads_waitForShardingInit.js
Branch: master
https://github.com/mongodb/mongo/commit/0883e00debf73e6e2fa4c5c0c06e7e856a71c5e6

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