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

Don't drop database from old primary shard after movePrimary

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.7.3
    • Fix Version/s: 3.7.4
    • Component/s: Sharding
    • Labels:
      None

      Description

      We should just drop the unsharded collections that were moved; there is no need to drop the whole database (and anyway, we only do that if there were no sharded collections), particularly since once unsharded collections are tracked as sharded collections with one chunk, it will be incorrect to drop the database.

      Changing the FCV 4.0 protocol to not drop the database will prevent us from having to change the protocol in a later release (and therefore handle upgrade/downgrade and mixed-version clusters in that release).

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: