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

Upgrade to 3.6 fails on name conflict with config database

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Upgrade/Downgrade
    • Labels:
      None
    • Sprint:
      Sharding 2019-07-01
    • Case:

      Description

      Presence of a user-defined database named config in a 3.4 replica set can result in the follow errors (followed by a BACKTRACE and instance failure) on upgrade to 3.6: 

      F -        [rsSync] terminate() called. An exception is active; attempting to gather more information
      		 
      F -        [rsSync] DBException::toString(): DatabaseDifferCase: Failed to create the config.transactions collection due to db already exists with different case already have: [Config] trying to create [config]
      		 
      Actual exception type: mongo::error_details::ExceptionForImpl<(mongo::ErrorCodes::Error)13297, mongo::AssertionException>

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: