[SERVER-30672] Integrate secondary chunk aware and causal consistency with secondary readPreference in jscore_passthrough suite Created: 15/Aug/17 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-test-improvements, sharding36-passthrough-testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-08-21, Sharding 2017-09-11, Sharding 2017-10-02, Sharding 2017-10-23 |
| Participants: |
| Description |
|
To enable the "secondary chunk aware" codepath need a test where |
| Comments |
| Comment by Misha Tyulenev [ 06/Sep/17 ] |
|
max.hirschhorn reopened per your request |
| Comment by Max Hirschhorn [ 06/Sep/17 ] |
misha.tyulenev, I think we'll still want to do this as the concurrency suite doesn't necessarily run all commands supported by MongoDB. |
| Comment by Misha Tyulenev [ 06/Sep/17 ] |
|
Per Max's comments the task is addressed in the concurrency suite |
| Comment by Max Hirschhorn [ 16/Aug/17 ] |
|
misha.tyulenev, given that the concurrency framework (1) already creates sharded collections, (2) runs with the balancer enabled, and (3) generally mixes doing reads and writes with multiple clients, I wonder if you'd have an easier time / get more out of starting with the concurrency framework and making it run with causal consistency + readPreference=secondary. We'll still want to eventually run both the concurrency suite version and the jsCore version under the configuration you've described. I've filed |