[SERVER-32920] Avoid overriding read preference for the config server in passthrough tests. Created: 26/Jan/18  Updated: 30/Oct/23  Resolved: 28/Mar/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.8, 3.7.4

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
causes SERVER-34248 Investigate why function_string_repre... Closed
Related
is related to SERVER-32468 Use a 1-node CSRS in non-stepdown sha... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: TIG 2018-02-26, TIG 2018-04-09
Participants:

 Description   

Avoiding setting secondary read preference to the config servers will allow us to run more sharding passthrough tests with a 1 node CSRS, improving test stability.

The read preference is overridden in set_read_preference_secondary.js

The causal consistency test suites should also use the above override, instead of setting the read preference directly.



 Comments   
Comment by Githook User [ 07/Sep/18 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}

Message: SERVER-32920 Avoid overriding read preference for the config server in passthrough tests

(cherry picked from commit fe88a7402503f76b43c7ee71ef45b4ac0b9e3db7)
Branch: v3.6
https://github.com/mongodb/mongo/commit/f3acd4a1e259b1f1fcdd51d23ad2519369257dbf

Comment by Githook User [ 28/Mar/18 ]

Author:

{'email': 'robert.guo@10gen.com', 'name': 'Robert Guo', 'username': 'guoyr'}

Message: SERVER-32920 Avoid overriding read preference for the config server in passthrough tests
Branch: master
https://github.com/mongodb/mongo/commit/fe88a7402503f76b43c7ee71ef45b4ac0b9e3db7

Comment by Robert Guo (Inactive) [ 26/Mar/18 ]

schwerin re your question from January. I would say, for the purpose of this ticket, using the default read preference is more stable; if for no other reason, it runs less test code, so fewer places to go wrong.

Comment by Andy Schwerin [ 26/Jan/18 ]

Would this be better or worse than using "secondaryPreferred" as the read preference for config servers in the passthroughs?

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