[SERVER-41841] Don't wait for speculative majority read concern when inside DBDirectClient Created: 20/Jun/19  Updated: 10/Jan/20  Resolved: 10/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Sprint: Repl 2019-10-21, Repl 2019-11-04, Repl 2020-01-27
Participants:
Linked BF Score: 4

 Description   

It is possible for us to run a command inside DBDirectClient when the parent operation is running under speculative majority read concern. In this case, we may hit this invariant if we have not set the read source yet. We should probably return immediately from waitForSpeculativeMajorityReadConcern since we should never need to do speculative majority waiting when inside a direct client operation.



 Comments   
Comment by William Schultz (Inactive) [ 10/Jan/20 ]

This was fixed by this commit from SERVER-40466 and the fix was backported to 4.2 (BACKPORT-5225). See comments on BF-13566 for a description of how it was fixed.

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