Define and generate new op entry types to match the commit of an addShard()

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-71755 defined new op entries to match the addition of databases to the config catalog when createDatabase or addShard are committed as a way to drive the management of cursors opened by nss/cluster.watch.

      Nevertheless, such solution is unable to support all the scenarios for the case of addShard - which should instead generate op entries describing the identity of a new shard as it gets added to the config catalog.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: