[SERVER-67790] [4.2] Running with enableMajorityReadConcern=false can commit behind the oldest/stable timestamp Created: 05/Jul/22  Updated: 02/Nov/22  Resolved: 05/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.21
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-55735 MongoDB version 4.2.5 WiredTiger erro... Closed
related to SERVER-55746 Validate inserts into the oplog of a ... Backlog
is related to SERVER-71008 Fatal assertion 39001 BadValue: times... Closed
Operating System: ALL
Participants:
Case:

 Description   

The bug manifests as seeing the following log line then crashing:

WiredTiger error (22) [1655379983:484753][134088:0x7f405d0d9700], WT_SESSION.timestamp_transaction: __wt_txn_set_commit_timestamp, 676: commit timestamp (1655379983, 851) is less than the oldest timestamp (1655379983, 854): Invalid argument Raw: [1655379983:484753][134088:0x7f405d0d9700], WT_SESSION.timestamp_transaction: __wt_txn_set_commit_timestamp, 676: commit timestamp (1655379983, 851) is less than the oldest timestamp (1655379983, 854): Invalid argument

This issue is specific to:

  • Running on 4.2
  • Running in replica set mode[1]
  • Running with enableMajorityReadConcern: false

To resolve the issue, it's recommended to turn enableMajorityReadConcern: true (the default) or upgrade to 4.4.

[1] Standalones can observe a similar symptom, but that is likely due to user error writing to the local.oplog.rs collection directly. See SERVER-55746.


Generated at Thu Feb 08 06:09:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.