[SERVER-30973] Load implicitly_shard_accessed_collections.js for secondary read preference causal consistency concurrency suite Created: 06/Sep/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: Jack Mulrow Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: AdiZ, sharding36-passthrough-testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-30974 Load implicitly_shard_accessed_collec... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

Add load('implicitly_shard_accessed_collections.js') to worker_thread.js if args.sessionOptions.readPreference is set. This ticket will involve investigating workloads that may be incompatible with the override and need to be blacklisted.

Some known blacklists are:

  • explain*.js workloads - they assert a collection does not exist, but the override may recreate it
  • reindex*.js workloads - they make assertions on the number of indexes, but an extra one will be created for {_id: "hashed"}

Potential blacklists:

  • drop_collection.js
  • kill_rooted_or.js, kill_aggregation.js

These workloads frequently timeout waiting for the distributed lock, which may be related to the override causing more load on the config server


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