Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12758

3.6 upgrade documentation should mention risk of failure when user-creates "config" database is present.

    XMLWordPrintableJSON

Details

    Description

      Description

      Upgrading replica set from 3.4 to 3.6 fails when a user-defined database name conflicts with the "config" database that needs to be created during upgrade.  (See SERVER-41350).

      This is definitely the case where there is a case mismatch (e.g., pre-existing database is named "Config" or "CONFIG") – when the pre-existing database is named "config" this is still incorrect, but the upgrade will probably succeed.

      Customers should be advised to check for and resolve naming conflicts with config database or config.sessions and  config.transactions collections before attempting to upgrade.

      Scope of changes

      • Update release notes upgrade guides to call this out
      • Backport work for DOCS-12757 to 3.4

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            mark.brinsmead@mongodb.com Mark Brinsmead
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago