Operational Defect Database

BugZero found this defect 2450 days ago.

MongoDB | 392263

[SERVER-29539] Visibility issues for readAfterClusterTime at level local

Last update date:

12/6/2022

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

When reading after a cluster time at level local, it is possible to have outstanding uncommitted transactions hide data assigned to an earlier cluster time. This is because optimes are not assigned by commit order. To fix this, we will need to block readAfterClusterTime reads until all transactions prior to the specified cluster time have committed. Note that it will be still be possible to return data before transactions after the specified cluster time have committed; this will be okay.

Top User Comments


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:

...