[SERVER-26170] Unify waitForReadConcern and waitForLinearizableReadConcern Created: 19/Sep/16  Updated: 06/Dec/22  Resolved: 09/Apr/20

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

Currently there are two separate calls for waiting for read concern - waitForReadConcern and waitForLinearizableReadConcern with the former also performing some linearizable read concern checks. This makes it confusing to decide which one should be used.

These two methods should be merged.



 Comments   
Comment by Siyuan Zhou [ 09/Apr/20 ]

waitForLinearizableReadConcern is to do a no-op write after the read operation, so as Judah mentioned they are for different purposes and cannot be unified. Shim added many indirect layers, so the implementation may not be obvious. Closing this as Won't Fix.

Comment by Judah Schvimer [ 19/Sep/16 ]

waitForReadConcern is called before we call run() on the command and waitForLinearizableReadConcern is called after we call run(), so we may not be able to unify them.

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