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

Handle ShardNotFound errors in the cleanup phase of the create coordinator

    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-04-29
    • 2

      In the new createCollectionCoordinator, hitting a ShardNotFound error triggers some updates to the list of involved shardIds. This prevents us from continuously trying to contact or otherwise involve a shard the has been removed.

      However, the _cleanupOnAbort function which is triggered by calling triggerCleanup does not have any onError handlers. This means that if an involved shard is removed while the create coordinator is running cleanup, the coordinator would continue to try to release the critical section on this removed shard.

            Assignee:
            adam.farkas@mongodb.com Wolfee Farkas
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: