[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
1. test fixture is a replica set (can use ShardedClusterFixture )
2. enable causal consistency and secondary readPreference
3. shard collections using sharded_collections_jscore_passthrough suite approach
4. has at least two shards in the fixture
5. move chunks while running the suite



 Comments   
Comment by Misha Tyulenev [ 06/Sep/17 ]

max.hirschhorn reopened per your request

Comment by Max Hirschhorn [ 06/Sep/17 ]

We'll still want to eventually run both the concurrency suite version and the jsCore version under the configuration you've described.

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 SERVER-30680, SERVER-30681, and SERVER-30682 to track the individual pieces of work for the concurrency suite version in case you're interested.

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