Operational Defect Database
BugZero found this defect 65 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2609834
Router must route `convertToCapped` without incorrect shard version
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
8.0.0-rc0
Description:
Info
Routers are forwarding convertToCapped commands to shards by using the executeCommandAgainstDatabasePrimary helper that is always attaching UNSHARDED shard version. The shard ignores the version when instantiating a DDL coordinator (that does not inherit parameters from the command's operation context), but this is not the case when executing the legacy path that is expecting the right shard version. There are 2 possible solutions: Route by using the executeDDLCoordinatorCommandAgainstDatabasePrimary helper that does not attach unconditionally the UNSHARDED version. Wait for SERVER-86309 that will properly unregister collections on downgrade (the real issue is that the FCV was downgraded without the collection getting unregistered from the sharding catalog)
Top User Comments
xgen-internal-githook commented on Fri, 15 Mar 2024 15:47:41 +0000: Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'} Message: SERVER-88037 Router must route `convertToCapped` without incorrect shard version (#20027) GitOrigin-RevId: 012de2a69e4e36a7acf9c90a1a2ce27b41baac8c Branch: master https://github.com/mongodb/mongo/commit/8e8995cac40c4457f10c9830db95299a2486766d
Steps to Reproduce
