[SERVER-33253] [passthrough testing] extend cluster catalog consistency hook to add checks for collection indexes and options Created: 09/Feb/18  Updated: 12/Jul/23  Resolved: 12/Jul/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1 Desired

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Tommaso Tocci
Resolution: Duplicate Votes: 0
Labels: RachitaD, open_todo_in_code, pm-1051-legacy-tickets
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-76293 Check that all the shards have exactl... In Progress
Related
related to SERVER-78905 Complete TODO listed in SERVER-33253 Blocked
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24
Participants:

 Description   

Collection indexes and options are part of the "sharding catalog," but rather than the config server, the primary shard for the collection's database is authoritative for these.

This ticket is to extend the cluster catalog consistency hook to read the authoritative list of collection indexes and options from the primary shard and check that all shards that own chunks for the collection have the same indexes and options.



 Comments   
Comment by Tommaso Tocci [ 12/Jul/23 ]

In PM-3020 we added checks for indexes, while in SERVER-76293 we will add checks for collection options

Comment by Esha Maharishi (Inactive) [ 09/Feb/18 ]

Note, this hook may have to account for Bug #1 and Bug #2 described in SERVER-31715.

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