Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.4, 5.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v5.0
Sprint:
Execution Team 2021-08-23
Linked BF Score:
25
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The fsync command on the secondary does not force the durable timestamp forward.

The test passes most of the time because the journal flusher updates the durable optime in the TopologyCoordinator before the test calls replSetGetStatus.

is related to

SERVER-56522 Use proper timestamp comparison in non_durable_writes_on_primary_can_reach_majority.js

Closed

SERVER-41386 Create a JS test that ensures non-durable writes can replicate but are not counted for majority write concern

Closed

SERVER-41387 Create a test that ensures the oplogTruncateAfterPoint will correctly clear writes on startup after a primary restarts

Closed

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User, Vivian Ge
Votes:: 0 Vote for this issue
Watchers:: 0 Start watching this issue

Created:: Aug 05 2021 10:41:41 PM UTC
Updated:: Oct 29 2023 09:49:50 PM UTC
Resolved:: Aug 13 2021 12:26:54 PM UTC
Confidence Status Last Update:: 12/Aug/21 6:17 PM