[SERVER-62007] Support majority read for listCollections Created: 13/Dec/21  Updated: 01/Mar/22  Resolved: 01/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Benety Goh
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-62006 Support majority read for _mdb_catalog Closed
Related
related to SERVER-62310 collMod command not sent to all shard... Closed
Sprint: Execution Team 2022-01-24, Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-03-07
Participants:

 Description   

In C2C replication, we would like to only replicate majority committed data so that we can avoid handling rollbacks of the source cluster. This is now done by using majority readConcern in collection scans in the cloning phase. However, listDatabases/listCollections/listIndexes don't support reading majority committed catalog as the catalog is not versioned. This makes it very hard for an external process to detect when the result returned by these list commands rolls back. This work is to support majority read for listCollections by reading from a majority committed snapshot of the _mdb_catalog without actually introducing versioned catalog.

And it should also work with sharded clusters.



 Comments   
Comment by Benety Goh [ 01/Mar/22 ]

The underlying problem described in this ticket has been resolved as part of SERVER-62006, which returns information in _mdb_catalog at the requested read snapshot that includes both databases and collections.

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