Operational Defect Database

BugZero found this defect 2386 days ago.

MongoDB | 416827

[SERVER-30665] applyOps collMod handling should only allow nonexistent UUIDs for UUID upgrade collMods

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.5.12

Description:

Info

Currently, a collMod oplog entry with a nonexistent UUID will be applied to an existing collection if the collection name of the oplog entry matches an existing collection name. This is due to the handling of collMods that are used to upgrade from 3.4 to 3.6 and add UUIDs to collections. This special handling should only occur for collMods that are for upgrade, i.e., empty collMods.

Top User Comments

xgen-internal-githook commented on Thu, 17 Aug 2017 18:36:37 +0000: Author: {'username': 'mvankeulen94', 'email': 'maria@mongodb.com', 'name': 'Maria van Keulen'} Message: SERVER-30665 Only accept nonexistent UUIDs for UUID upgrade collMods Branch: master https://github.com/mongodb/mongo/commit/c1aaff64cdf88d3ff2f0220033964fa6fcdb5513

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...