[SERVER-59442] Prototype database rename Created: 19/Aug/21  Updated: 04/Feb/22  Resolved: 29/Sep/21

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Yuhong Zhang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Sprint: Execution Team 2021-09-06, Execution Team 2021-09-20, Execution Team 2021-10-04
Participants:

 Description   

There is a long-standing request (SERVER-701) about the lack of capability to rename databases.

Now when we are rid of MMAPv1 it might be possible to support database renaming in some circumstances. We should investigate the effort needed to support it.

Going to need a new command and oplog entry to perform the database rename.

  • What kind of locking do we need to do? Global exclusive or exclusive database? Global IX?
  • What restrictions must we have? Probably no directoryperdb.
  • How would it impact replication rollback?
  • How would it impact sharding?
  • How would it impact encryption at rest?
  • How to relax constraints for initial sync/applyOps (e.g: MongoMirror)

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