-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Server Serverless 2022-08-08, Server Serverless 2022-08-22, Server Serverless 2022-09-05, Server Serverless 2022-09-19
When applying operations from the oplog, secondaries apply ops individually (except for inserts that can be grouped together). After SERVER-66708, the NamespaceString on each individual op should already contain the tenantId in the "tid" field, so this ticket is mainly about testing that this works - we can also add an invariant that the tenantId in the "ns" field matches that in the "tid" field in OplogApplierUtils::applyOplogEntryOrGroupedInsertsCommon.
We can add unit tests checking that we can apply inserts, deletes, and updates correctly in OplogApplierImplTest (in oplog_applier_impl_test.cpp). Note we cannot test applying writes that are part of multi-document transactions until we correctly handle applying transaction commands as well.
- depends on
-
SERVER-61994 Change CollectionCatalog maps that are keyed by NamespaceString to be keyed by TenantNamespace
- Closed
-
SERVER-62780 Create tenantId decoration on opCtx for use by background threads
- Closed
- is depended on by
-
SERVER-69726 Run multitenancy tests on replica sets
- Closed