[SERVER-50985] Tenant collection cloner query must use readConcern majority Created: 16/Sep/20  Updated: 29/Oct/23  Resolved: 15/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-D
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-53294 TenantMigrationRecipientService not a... Closed
duplicates SERVER-53293 DBClientCursor not properly applying ... Closed
Related
is related to SERVER-53293 DBClientCursor not properly applying ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-11-30, Repl 2020-12-14, Repl 2020-12-28
Participants:

 Comments   
Comment by Githook User [ 15/Dec/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}

Message: SERVER-50985 Tenant collection cloner query must use readConcern majority
Branch: master
https://github.com/mongodb/mongo/commit/bb3279a62dfc65bdafa5164a7ce85c8322b4757b

Comment by Jason Chan [ 09/Dec/20 ]

Due to the issue discussed in SERVER-53293, we can't just pass in readConcernMajority as an argument to DBClientConnection::query. Instead, we should explicitly add the readConcern value to the query BSON.

Comment by Judah Schvimer [ 29/Sep/20 ]

Pausing progress on this since it's not actually necessary for milestone B. I'll pick it back up since I have some WIP on it once milestone B is complete.

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