[SERVER-63454] Don't require tenantId for shard merge Created: 08/Feb/22  Updated: 29/Oct/23  Resolved: 15/Aug/22

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-63596 Exclude last LTS from multiversion se... Open
depends on SERVER-61145 Start fetching donor oplog entries Closed
depends on SERVER-61146 Apply donor oplog entries Closed
depends on SERVER-63122 Remove logical cloning procedure for ... Closed
is depended on by SERVER-59492 Post-Merge cleanup Closed
is depended on by SERVER-59794 Make existing tenant migration js tes... Closed
Duplicate
is duplicated by SERVER-59794 Make existing tenant migration js tes... Closed
is duplicated by SERVER-63979 Ban tenantId with protocol "shard merge" Closed
Related
related to SERVER-61231 Adapt migration tests for shard merge Closed
is related to SERVER-65352 Complete TODO listed in SERVER-59794 Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-03-21, Server Serverless 2022-04-04, Server Serverless 2022-04-18, Server Serverless 2022-05-02, Server Serverless 2022-05-16, Server Serverless 2022-05-30, Server Serverless 2022-07-11, Server Serverless 2022-07-25, Server Serverless 2022-08-08, Server Serverless 2022-08-22
Participants:

 Description   

The "tenantId" parameter is optional for the donorStartMigration and recipientSyncData commands (SERVER-59495), but Shard Merge currently doesn't work if you don't pass a tenantId.



 Comments   
Comment by Christopher Caplinger [ 16/Aug/22 ]

looks like something went awry with the git hook that comments the commit, manually adding here:

SERVER-63454: Don't require tenantId for shard merge
Branch: master
https://github.com/mongodb/mongo/commit/e455a0fa9c571753bf07d4c951bfbf881005c3a7

Comment by A. Jesse Jiryu Davis [ 17/Mar/22 ]

Without a tenantId, TenantMigrationRecipientOpObserver::onUpdate will have to skip its call to createAccessBlockerIfNeeded when protocol is "shard merge". But that's ok, because SERVER-61141 will install recipient access blockers during file import.

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