CatalogCache should mark database entry as needs refresh on encountering ShardNotFound when trying to get primary shard's Shard object

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • v4.0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This fixes a regression introduced in 4.0.

      However, a user should be running flushRouterConfig against all routers and shards after a dropDatabase or movePrimary, which would prevent this and other issues from occurring.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: