Invalid authoritative knowledge on secondary node after move primary locally creates the collection on the primary shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 7.3.4, 8.0.0-rc10, 7.0.13, 6.0.20, 5.0.31
    • Affects Version/s: 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.2.0, 8.0.0-rc0, 7.3.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0, v6.0, v5.0
    • Hide

      issue.js

      Show
      issue.js
    • CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10
    • 200
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The movePrimary operation might need to create a representation of sharded collections in the new primary shard during the cloning phase.  During the creation of these collections, an Op Observer will set the CollectionShardingRuntime  as UNKNOWN, but only on the primary node. Thus, secondary nodes will keep whatever state they previously had (if any). 

        1. issue.js
          2 kB

            Assignee:
            Antonio Fuschetto
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: