Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-9884

repairDatabase command disables profiling, doesn't copy system.profile collection

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.5.0
    • Admin
    • Replication
    • ALL

    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.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            rassi J Rassi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: