[SERVER-34493] Check whether or not to read from the last applied timestamp before accessing the value Created: 16/Apr/18  Updated: 29/Oct/23  Resolved: 17/Apr/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.7.4
Fix Version/s: 3.7.5

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
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
Sprint: Storage NYC 2018-04-23
Participants:
Linked BF Score: 33

 Description   

A BF is caused by calling ReplicationCoordinator::getMyLastAppliedOpTime() before checking if we should. On embedded, which hits a MONGO_UNREACHABLE.

We should change the logic to check whether or not to read the timestamp before accessing it.



 Comments   
Comment by Githook User [ 17/Apr/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-34493 Check whether or not to read from the last applied timestamp before accessing the value
Branch: master
https://github.com/mongodb/mongo/commit/6740732f3a331372127369e423cb257b2cdd6ccf

Comment by Louis Williams [ 16/Apr/18 ]

Waiting for 3.7.4 release

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