[SERVER-9459] Alias repairDatabase/repair to rebuildDatabase/rebuild Created: 25/Apr/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: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 4
Labels: compaction, rebuild, repair, repairDatabase
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-11923 Add a non-lossy repairDatabase analog. Closed
is related to DOCS-1291 Database repair warning missing context Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

We have two different use cases for doing a "repair":

  • Unclean shutdown, no good backup nor replicas, and you want to recover to a working state (understanding you may lose data)
  • Compaction and/or rebuilding the db files

The docs cover and warn about the first case, but if you are doing the second those warnings are confusing and inappropriate. It is also very confusing to tell or explain they need to do a repair when really we want them to do the second thing.

We may want to deprecate and remove repair/repairDatabase in the future as well.



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

The repairDatabase command has been removed.

Comment by Asya Kamsky [ 17/Apr/14 ]

It would be really good if there were different names for something that defragments and aborts in case of error/malformed bson, and something that's exclusively for attempts to recover partially recoverable data from known invalid/corrupt DB.

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