[SERVER-11923] Add a non-lossy repairDatabase analog. Created: 02/Dec/13  Updated: 06/Dec/22  Resolved: 01/Oct/18

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

Type: New Feature Priority: Major - P3
Reporter: Richard Kreuter (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 3
Labels: repairDatabase
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-1291 Database repair warning missing context Closed
related to SERVER-9459 Alias repairDatabase/repair to rebuil... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Problem: in the presence of corruption, repairDatabase is lossy and almost never the right thing to use, but in the absence of corruption, repairDatabase is non-lossy and a valid way to compact a database's file set. This has lead to complex documentation, education, and customer support issues about whether and when it's safe to run the command.

Proposal: introduce a new command that does what repairDatabase currently does, but that aborts and cleans up after itself when corruption is encountered. (For the purpose of discussion, let's call this "rebuildDatabase".)
This way, we can document rebuildDatabase as a safe, non-lossy way to compact a database, and repairDatabase as the last ditch recovery mechanism that people should exercise extra care about using.

Documentation changes needed: document a new command. Clarify documentation about an old command.



 Comments   
Comment by Eric Milkie [ 01/Oct/18 ]

The repairDatabase command has been removed, and the current way to compact a database is to use the compact command.

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