Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-40709

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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Sharding
    • Sharding
    • v4.0

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32871 ReplicaSetMonitorRemoved and ShardNotFound errors on fanout query after removing a shard

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: