[SERVER-53294] TenantMigrationRecipientService not actually using majority read concern Created: 09/Dec/20  Updated: 06/Dec/22  Resolved: 09/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-50985 Tenant collection cloner query must u... Closed
Related
is related to SERVER-53293 DBClientCursor not properly applying ... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

Due to the issue described in SERVER-53293, the TenantMigrationRecipientService is not actually using majority read concern when making DBClientConnection calls to get the latest majority committed entries in the oplog and transactions table(eg. here and here).



 Comments   
Comment by Jason Chan [ 09/Dec/20 ]

This will be fixed as part of SERVER-50985.

Comment by Jason Chan [ 09/Dec/20 ]

This can be marked as a dupe if we decide SERVER-53293 is actually a bug and that ticket includes a fix.

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