Operational Defect Database
BugZero found this defect 233 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2454982
Transaction limit can be hit in addShard
Last update date:
3/12/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
SERVER-71755 added code to insert the shard metadata along with the database metadata and the placement history in a transaction as part of PM-1939, this fixes addShard not registering all the databases if there is a failure in the middle of the write operation, and allows a stable timestamp to get the necessary metadata for change streams, however, a replica set with too many databases could have a similar problem as the one described in SERVER-58433, where we reach the limits of the WiredTiger cache size for a transaction. SERVER-79160 adds to that transaction the collections present in the shard, making this problem more probable. We should batch the request in several transactions to mitigate this, until we have a fully reliable addShard which should come in PM-2050.
Top User Comments
Steps to Reproduce
