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

changePrimary should fail if it encounters unexpectedly untracked collections

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing

    Description

      After the track unsharded project completes, the only collections expected to be moved by changePrimary (using the movePrimary coordinator) are those that are client system namespaces. Any other collections should be tracked, and their presence indicates a problem in the sharding metadata.

      If changePrimary encounters some untracked collection it does not expect, it should throw an error.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: