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

moveChunk will keep on returning ShardNotFound until DatabaseVersion is updated

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.16
    • Component/s: Sharding
    • None
    • Sharding
    • ALL

      At the beginning of chunk migration, we do a force refresh of the collection metadata, this will eventually call CatalogCache::_getCollectionRoutingInfoAt, which will then call CatalogCache::getDatabase. getDatabase, however will always try to call ShardRegistry::getShard of what it thinks is the current primary database. If the shard has already been removed, then it error out with ShardNotFound.

      To get around this issue, send a flushRouterConfig to the affected shard.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: