Generate NamespacePlacementChanged on addition of first shard in the sharded cluster

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-12-08
    • 🟥 DDL, 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Context (projection_fakes_internal_event.js):

      • 2 shard sharded cluster
      • projection_fakes_internal_event.test collection is being created and 5 documents are inserted. It's placed on shard 1
      • we open a collection change stream at time (1, 1)
      • consult placement history for timestamp (1, 1)
      • retrieve placement history in form of shard0 (initialization marker data)
      • wait forever and don't observe any events, because the events for that database are present on shard 1, but no event is emitted on shard 0 for us to update the set of tracked shards

            Assignee:
            Paolo Polato
            Reporter:
            Denis Grebennicov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: