-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: Layered Tables
-
Storage Engines - Foundations
-
None
-
None
[j2:sec] | 2025-10-21T22:02:36.566+00:00 F ASSERT 23081 [conn60] "Invariant failure","attr":{"expr":"!TestingProctor::instance().isEnabled()","msg":"cursor returned out-of-order keys","location":"src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp:1726:95:void mongo::WiredTigerRecordStoreCursorBase::reportOutOfOrderRead(const RecordId &, bool) const"}
Seen in a patch build from running disagg_repl_jscore_passthrough with 2 nodes with the validate collections in background hook (in job2)
Could be related to BF-39706 but that was already closed.
- causes
-
WT-16172 Coverity analysis defect 183953: Missing unlock
-
- Closed
-
-
WT-16173 Coverity analysis defect 183950: Missing unlock
-
- Closed
-
-
WT-16174 Coverity analysis defect 183951: Dereference of potentially null field
-
- Closed
-
- is depended on by
-
SERVER-111356 Create disagg_two_nodes_repl_jscore_passthrough
-
- Closed
-
- is related to
-
SERVER-112719 Early exit verify in disagg
-
- Closed
-
-
WT-15629 (disagg.mode=leader) Test/format key OOO (internal page delta)
-
- Closed
-
-
WT-15826 test/format (disagg.mode=leader, PALM) OOO keys detected
-
- Closed
-
- related to
-
WT-15829 Implementation: Data Consistency Validation for Multi-Node in Disagg (test/format)
-
- Open
-
-
WT-15189 test/format disagg follower and Python tests time out in clayered_next_random
-
- Open
-