Operational Defect Database
BugZero found this defect 72 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2602859
RefineCollectionShardKeyCoordinator should not use filtering metadata cache utilities to fetch routing information
Last update date:
3/12/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
8.0.0-rc0
Description:
Info
The RefineCollectionShardKeyCoordinator requires up-to-date routing information to perform cross-shard validations on the refined shard key candidate, but it is using a method of the "Filtering Metadata Cache API" to obtain it. While this solution works today, SERVER-84243 will cause such logic not to work in the intended way.
Top User Comments
xgen-internal-githook commented on Tue, 12 Mar 2024 17:57:51 +0000: Author: {'name': 'ppolato', 'email': '82828243+ppolato@users.noreply.github.com', 'username': 'ppolato'} Message: SERVER-87693 Avoid using onCollectionPlacementVersionMismatch to get refreshed routing info in RefineCollectionShardKeyCoordinator (#19762) GitOrigin-RevId: 73001b7700e0ce60fa9a04eb105548294e2870c6 Branch: master https://github.com/mongodb/mongo/commit/056c373bed0152601b2e98449b5c1087ad3822d0
Steps to Reproduce
