[SERVER-32883] Enhanced FSM testing for reading from secondaries Created: 24/Jan/18 Updated: 30/Oct/23 Resolved: 23/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | TIG 2018-05-07, Storage NYC 2018-05-07, Storage NYC 2018-05-21, Storage NYC 2018-06-04 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
1. Change the secondary_reads_passthrough.yml test suite which was added as part of 2. Add a new version of the concurrency_replication.yml test suite that uses a 5-node replica set with each secondary syncing in succession of each other (i.e. a linear chain), writeConcern={w: 1}, readConcern={level: "local", afterClusterTime: ...}, and readPreference={mode: "secondary"}. We'll also likely want to make a wrapper around a Mongo connection object to the primary and to a specific secondary so that an individual worker thread talks to a particular secondary all the time rather than some secondaries potentially never being read from.
In creating this wrapper around two separate Mongo connection objects, we may also want to change how Original descriptionAs part of We should have a passthrough test where we test these behaviors. This is related to |
| Comments |
| Comment by Githook User [ 24/May/18 ] |
|
Author: {'username': 'xy24', 'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com'}Message: (cherry picked from commit 73cf3829a07f09bf35e1563a8cd0c1bad74bc226) |
| Comment by Githook User [ 23/May/18 ] |
|
Author: {'username': 'xy24', 'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 24/Jan/18 ] |
|
geert.bosch, why did the fix for |
| Comment by William Schultz (Inactive) [ 24/Jan/18 ] |
|
I agree that a passthrough suite exercising various chaining configurations could be valuable. A 5-node replica set, for example, would have a number of different chaining topologies that would be good to test. It seems like an area where our test coverage may be lacking. |
| Comment by Max Hirschhorn [ 24/Jan/18 ] |
|
geert.bosch, is this your idea of having a version of replica_sets_jscore_passthrough.yml where we have 2 secondaries and force one of them to chain off of the other? |