[SERVER-61341] Support collection rename in tenant migrations Created: 09/Nov/21  Updated: 03/Apr/23  Resolved: 03/Apr/23

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: FY23Q1-cand
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-61299 Crash when donor collection is rename... Closed
Assigned Teams:
Serverless
Participants:

 Description   

If a donor collection is renamed during a tenant migration, the recipient aborts the migration. Possible mechanism:

  1. Recipient opens cursor on donor collection by UUID.
  2. Recipient clones some documents.
  3. Renaming the collection on the donor kills the cursor.
  4. The recipient considers the error retryable, and opens a new cursor on the renamed collection (by the same UUID).
  5. Using the new cursor, the recipient begins cloning from the beginning.
  6. The recipient tries to insert the same first document, generating a DuplicateKeyError.

I'm not sure this is the correct diagnosis. And, once the DuplicateKeyError is fixed, make sure the recipient ends up with a collection that is properly named, and does not have a collection with the old name.



 Comments   
Comment by Didier Nadeau [ 03/Apr/23 ]

As this only impacts Tenant Migration and we expect to sunset it, I'm closing it as won't do.

Comment by Didier Nadeau [ 29/Mar/23 ]

Moving it to "needs scheduling" to discuss it at triage. I expect we'll close it as won't do given we decided not to improve Tenant Migration anymore.

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