[SERVER-5106] Ability to restore the data files for a given DB without shutting down the mongod process Created: 27/Feb/12  Updated: 06/Dec/22  Resolved: 18/Dec/18

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

Type: New Feature Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-3270 Add {closeDatabase: ...} command Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Problem:
There are events that may cause an administrator to want to restore specific databases in a running mongod process. For example, in a multi-tennat situation where each DB is associated with a tenant. You may want to restore one database from a backup but not take the mongod process for all the other tenants.

You can call closeAllDatabases which will essentially forces the mongod process to reload the data files.

Solution:
a) ensure that this use case is tested and support across all platforms
b) provide a mechanism to "lock" the database during the restore, to prevent a client connect trying to create the database and/or collections, indexes etc. while the restore is in progress.


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