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

moveChunk will keep on returning ShardNotFound until DatabaseVersion is updated

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 4.0.16
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Case:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: