Operational Defect Database

BugZero found this defect 2503 days ago.

MongoDB | 375869

[SERVER-28883] Avoid the scenario when KeyManager creates 2 keys with close expiration

Last update date:

1/29/2018

Affected products:

MongoDB Server

Affected releases:

3.5.6

Fixed releases:

No fixed releases provided.

Description:

Info

Imagine the scenario of the node1 that is a primary becomes secondary while the node2 becomes a new primary. If the key expiration coincides with the transition its possible that node1 writes a new key just before it stops being primary and node2 reads the stale cache and adds another key. As a result the system.keys collection will have two different keys with the close expiresAt values. This can lead to the scenario when the key is not available to a secondary when 2 keys with close expiration just expired but the new key is not added by a KeyUpdater because the node has a clock skew.

Top User Comments

misha.tyulenev commented on Tue, 13 Jun 2017 19:32:25 +0000: The fix for SERVER-28972 will make this scenario unfeasible.

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:

...