[SERVER-9884] repairDatabase command disables profiling, doesn't copy system.profile collection Created: 09/Jun/13  Updated: 06/Dec/22  Resolved: 23/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: repairDatabase
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

Running the repairDatabase command turns off the database profiler after the repair completes. The repairDatabase command should set the profiling level of the repaired database to be the same as that of the pre-repaired database.

In addition, the repairDatabase command doesn't copy the system.profile collection. repairDatabase is implemented using Cloner(), which does not clone any system.* collections except system.users, system.js and system.indexes. It is is expected behavior for system.profile to be omitted when using Cloner() for initial sync, but it is not expected for system.profile to be omitted when using Cloner() for repairDatabase.



 Comments   
Comment by Spencer Brody (Inactive) [ 23/Aug/18 ]

The repairDatabase command is removed in master

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