[SERVER-83977] Core list_catalog.js should take into account the createIndex might not hit every shard Created: 07/Dec/23 Updated: 22/Dec/23 Resolved: 22/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.3.0-rc0 |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Enrico Golfieri | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | CAR Team 2023-12-25 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 147 | ||||||||
| Description |
|
The test perform:
After a first check, the collection runs $listCatalog Collectionless (against the adminDb) and later ensures that every entry (local catalog of shard X) has a fixed expected number of indexes. This test always works on any suite because:
Until now the createIndex always targetted either the primary or every shard, ensuring to have the expected number of indexes on every non-empty entry After the introduction of the "unsplittable_collections_on_any_shard_jscore_passthrough" we now create a the collection on a random shard using the createUnsplittableCollection test command. In case the collection is not created on primary we have a situation where:
This leads the test to fail since the number of expected indexes on the first shard does not match.
|
| Comments |
| Comment by Githook User [ 22/Dec/23 ] |
|
Author: {'name': 'Marcos Grillo', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: GitOrigin-RevId: 278271d7e4b5bd41b43e93080a29ae503c37086d |