[SERVER-34192] Secondary reads during batch applications Created: 29/Mar/18  Updated: 29/Oct/23  Resolved: 13/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 3.7.4

Type: New Feature Priority: Critical - P2
Reporter: Geert Bosch Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-20328 Allow secondary reads while applying ... Closed
Problem/Incident
Related
related to SERVER-21307 Replicated DDL (catalog) operation du... Closed
is related to SERVER-34590 oplog visibility issues with round_to... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-04-09, Storage NYC 2018-04-23
Participants:
Case:
Linked BF Score: 72

 Comments   
Comment by Andy Schwerin [ 15/Apr/18 ]

I see the problem. It's the way we're constructing the optional
lastAppliedTimestamp:

lastAppliedTimestamp = boost::make_optional(
readAtLastAppliedTimestamp,
replCoord->getMyLastAppliedOpTime().getTimestamp());

We should instead build it in such a way that when readAtLast... Is false,
we don't ask for the last applied time. Easy peasy.

Comment by Andy Schwerin [ 15/Apr/18 ]

That is surprising. The call to canAcceptWritesFor should be returning true
in the embedded coordinator in all circumstances, which ought to make
_shoukldDo... return false...

Comment by Githook User [ 13/Apr/18 ]

Author:

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

Message: SERVER-34192 Allow secondary reads during batch applications
Branch: master
https://github.com/mongodb/mongo/commit/10bcc73a75ac857c290c3af6a3f89a45c4867043

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