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

Removal of recordIdsReplicated leaves inconsistent metadata on downgrade for sharded clusters

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing

      Currently, for testing purposes, the recordIdsReplicated option is being removed automatically on downgrade. This was done as part of SPM-2983. The current implementation does not take into account any sharding guarantees, like stopping migrations, holding DDL locks, or honoring critical sections. This leaves the possibility to have inconsistent metadata across shards temporarily.

      WRITING-25576 describes a correct procedure to update catalog metadata on sharded clusters. The purpose of this ticket is to follow that design to prevent having metadata inconsistencies when removing recordIdsReplicated on downgrade in a sharded cluster.

            Assignee:
            Unassigned Unassigned
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: