Operational Defect Database

BugZero found this defect 2503 days ago.

MongoDB | 375870

[SERVER-28884] CollectionRangeDeleter track deletions more reliably

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

3.5.7

Fixed releases:

3.5.7

Description:

Info

In current code, each metadata version has provisioned one range to delete when it is retired. Registering a second range would require copying the metadata to a new version (if there is no other event that required the copy), a potentially expensive operation. Keeping a list of ranges for each metadata version would simplify the code and avoid otherwise-unnecessary metadata copying. Furthermore, the event-managing code has a race in which a deletion could fail while the requester is not waiting, resulting in the failure not being reported to the requester, and then, possibly, in-migration to a range currently occupied. Solving this requires plumbing range deletion event notification through more levels of interface.

Top User Comments

xgen-internal-githook commented on Wed, 17 May 2017 17:53:42 +0000: Author: {u'username': u'ncm', u'name': u'Nathan Myers', u'email': u'ncm@cantrip.org'} Message: SERVER-28884 Better range deletion event tracking Branch: master https://github.com/mongodb/mongo/commit/1ac2f9d964bc86a1b7ed5ec608a7d1c444b017bd nathan.myers commented on Mon, 15 May 2017 21:55:00 +0000: See also comments on 133320002: https://mongodbcr.appspot.com/133320002/#msg3 https://mongodbcr.appspot.com/133320002/#msg4

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:

...