Operational Defect Database
BugZero found this defect 94 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2577524
CollMod coordinator use possibly stale database information
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
6.0.0
7.0.0
7.3.0-rc0
Fixed releases:
8.0.0-rc0
7.0.8
Description:
Info
As explained in SERVER-86671 it is not safe to access database information contained in the CollectionRoutingInformation when inside a DDL coordinator. Thus we should stop doing that in the CollMod coordinator. In this case we could simply use the current shard id since the coordinator is guarantee to be running on the database primary shard.
Top User Comments
xgen-internal-githook commented on Fri, 15 Mar 2024 15:11:58 +0000: Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'} Message: SERVER-86672 Update CollModCoordinator to use the current shardId as the id of the primary shard (#19924) GitOrigin-RevId: cadbf4b733557e95dde1173fe0344ed0a961ae72 Branch: v7.0 https://github.com/mongodb/mongo/commit/6e010fdd7b82f18b9def46f0e1821dc56455410a xgen-internal-githook commented on Thu, 14 Mar 2024 12:50:18 +0000: Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'} Message: SERVER-86672 Update CollModCoordinator to use the current shardId as the id of the primary shard (#19924) GitOrigin-RevId: e30f6c524f03f8925c25a7526396ad559aba0a5f Branch: master https://github.com/mongodb/mongo/commit/4152cbe76fbc35eb86da34c4d93332803d535374
Steps to Reproduce
