[SERVER-67344] Prevent dropping shard split or tenant migration/merge collections in serverless mode Created: 16/Jun/22  Updated: 06/Oct/23  Resolved: 06/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Didier Nadeau Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Serverless
Participants:

 Description   

Dropping the collection(s) containing shard split or tenant migration/merge state document result in deleting all tenant access blockers shard split tenant migration.

When we'll have both merge and split active, this will cause issues as dropping collection for one could remove blockers for the other (which could have an active operation).

A solution would be to prevent dropping either collection in serverless mode. If a user wants to delete the collection (for maintenance, dealing with issues, etc), the node can be restarted in non-serverless mode.



 Comments   
Comment by Didier Nadeau [ 06/Oct/23 ]

Not needed because we have a test to verify what happens if we drop the collection.

Comment by Suganthi Mani [ 27/Jun/22 ]

Note: We have existing tenant migration test to see whether migration work correctly if the state doc is dropped accidentally while the migration is in progress - tenant_migration_drop_state_doc_collection.js

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