[SERVER-72230] Ensure Shard Merge supports transactions Created: 17/Dec/22  Updated: 29/Oct/23  Resolved: 19/Jan/23

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

Type: Bug Priority: Major - P3
Reporter: Christopher Caplinger Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: change-streams-support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-72354 Confirm that all change collection en... Closed
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2023-01-09, Server Serverless 2023-01-23
Participants:

 Description   

We write a "fake" applyOps with ns set to tenantId_ here and here

For shard merge, we won't have a tenant id, so the namespace string will end up looking like _., which is invalid when multitenancy is enabled, which means application of txn entries will fail.

We can't simply skip setting nss for Shard Merge because entries require nss to be set: https://github.com/10gen/mongo/blob/d84272507b3957ce6289a6545e53cb25331a88d6/src/mongo/db/repl/oplog_entry.idl#L77-L80

We should be able to set nss to NamespaceString(boost::none, "") for shard merge. As part of this ticket, we should add/update tests for <16MB transactions



 Comments   
Comment by Githook User [ 19/Jan/23 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-72230: Ensure Shard Merge supports transactions
Branch: master
https://github.com/mongodb/mongo/commit/6a1a422e824c7d8cf0966a72021b595a0646e896

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