Presence of system.profile collections impairs transitionToDedicated completion

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.0.0, 8.2.0
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-02-02, CAR Team 2026-02-16
    • 2
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      When the profiler is enabled on a database, a collection DBNAME.system.profile is created on single shards. Given that the collection is local, it is not considered movable via moveCollection nor via movePrimary.

      When transitioning to dedicated config server, collections/databases are moved off via moveCollection/movePrimary and then this check makes sure that no collection on user databases is still containing data.

      Since the profiling collection is always skipped, transitioning to dedicated may fail because of that.

            Assignee:
            Wolfee Farkas
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: