Investigate why getShardMap might return a stale topology on multiple mongos-es

XMLWordPrintableJSON

    • Catalog and Routing
    • 200
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      getShardMap just forward to the user the shard registry content. 
      On multi-router testing, when multiple mongos are deployed, some mongos might have  a stale shard registry.
      This test (which compare listShards and getShardMap results) has been wrapped by an assert soon to handle this case. 
      We should investigate whether this is expected (this can happen even when no add/remove shard are occurring in background ) and whether update the documentation 

            Assignee:
            Unassigned
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: