Improve setFeatureCompatibilityVersion 4.2 impact with many tables

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a primary executes setFCV("4.2") its main work is to upgrade all its unique indexes to a new format (SERVER-32825). It writes a collMod oplog entry per collection to trigger the secondaries to upgrade their unique indexes too.

      When mongos executes setFCV, it sends it to the primary of the config replica set, which sends it to the primary of each shard, and waits for majority acknowledgement.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Dmitry Agranat
            Votes:
            0 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: