[SERVER-50963] rollback_via_refetch_anomaly.js fails on inMemory storage engine Created: 15/Sep/20  Updated: 29/Oct/23  Resolved: 29/Sep/20

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

Type: Bug Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 38

 Description   

Observed in the 4.0 branch:

assert.soon failed, msg : Could not find log entries containing the following message: We cannot transition to SECONDARY state because our 'lastApplied' optime is less than the initial data timestamp and enableMajorityReadConcern = false
contains@src/mongo/shell/check_log.js:58:1
@jstests/replsets/rollback_via_refetch_anomaly.js:168:1



 Comments   
Comment by A. Jesse Jiryu Davis [ 21/Sep/20 ]

Note to self: this appears to be a problem with the test only on 4.0. I'll update the fix version once I've diagnosed the failure.

Generated at Thu Feb 08 05:24:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.