[SERVER-51902] Check if storage engine supports Recover to Stable Timestamp rather than if eMRC=false in sync_tail.cpp Created: 30/Oct/20  Updated: 29/Oct/23  Resolved: 17/Nov/20

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

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Repl 2020-11-02, Repl 2020-11-16, Repl 2020-11-30
Participants:
Linked BF Score: 25

 Description   

We invariant if eMRC is not false here because we assume that it's the only situation where the node has completed a rollback via refetch. But on 4.0 if the node is using an inMemory storage engine, it will also not support recover to a stable timestamp, meaning the node could have gone through a rollback via refetch.



 Comments   
Comment by Githook User [ 17/Nov/20 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-51902 Check if storage engine supports Recover to Stable Timestamp rather than if eMRC=false in sync_tail.cpp
Branch: v4.0
https://github.com/mongodb/mongo/commit/69ecb273de30c1435db59652a74b05fcda74fe8e

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