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

repairDatabase command on a new, different-cased database terminates server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.3
    • Fix Version/s: 3.5.1
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage 2016-11-21, Storage 2016-12-12
    • Case:
    • Linked BF Score:
      0

      Description

      In versions prior to 3.3.3, running repairDatabase on a new, different-cased database returns this error:

      {
      	"ok" : 0,
      	"errmsg" : "db already exists with different case already have: [a] trying to create [A]",
      	"code" : 13297
      }
      

      In 3.3.3+, the same command terminates the server:

      2016-04-28T16:11:12.503-0400 F STORAGE  [conn1] Unexpected exception encountered while reopening database after repair.
      2016-04-28T16:11:12.503-0400 F -        [conn1] terminate() called. An exception is active; attempting to gather more information
      2016-04-28T16:11:12.560-0400 F -        [conn1] DBException::toString(): 13297 db already exists with different case already have: [a] trying to create [A]
      Actual exception type: mongo::UserException
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              kamran.khan Kamran K.
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: