Upgrade to 3.6 fails on name conflict with config database

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Upgrade/Downgrade
    • None
    • Sharding 2019-07-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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>

              Assignee:
              Mira Carey
              Reporter:
              Mark Brinsmead
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: