Operational Defect Database

BugZero found this defect 2383 days ago.

MongoDB | 416901

[SERVER-30671] Don't expect operationTime to not change in causal_consistency_shell_support.js

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

3.5.11

Fixed releases:

3.6.3

3.7.1

Description:

Info

Internal activity in the config server can lead to writes that advance operationTime, which can cause causal_consistency_shell_support.js to fail when it asserts that read commands don't advance operationTime. This check should be removed since there is no way to either prevent or ignore these writes. This is the same base problem as SERVER-29111, but is triggered less frequently, only failing in suites with either more CSRS activity or that run more slowly (I've seen failues in sharding-auth and the continuous stepdown suite).

Top User Comments

xgen-internal-githook commented on Tue, 16 Jan 2018 21:52:02 +0000: Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'} Message: SERVER-30671 Don't expect operationTime to not change in causal_consistency_shell_support.js (cherry picked from commit 1b3d16dc0ecfac35dbbf945a3a9f6a8cdd3226f7) Branch: v3.6 https://github.com/mongodb/mongo/commit/b7656403b0ba229ccbe45ebc5506218eef8f5411 xgen-internal-githook commented on Fri, 1 Dec 2017 18:06:11 +0000: Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'} Message: SERVER-30671 Don't expect operationTime to not change in causal_consistency_shell_support.js Branch: master https://github.com/mongodb/mongo/commit/1b3d16dc0ecfac35dbbf945a3a9f6a8cdd3226f7

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:

...