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

Stop range deletion when hashed shard key index does not exist

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 5.0.22, 7.0.3, 6.0.12
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v7.0, v6.0, v5.0
    • Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04
    • 152

      Currently, range deletion gets stuck searching for an index to complete an indexScan for deletion. In the case of a hashed shard key index, we will allow skipping range deletion for the collection. This may lead to orphan documents remaining on the shards, but we will solve this with documentation by recommending that a user drain orphan documents before deleting their index.

            sanika.phanse@mongodb.com Sanika Phanse (Inactive)
            sanika.phanse@mongodb.com Sanika Phanse (Inactive)
            0 Vote for this issue
            3 Start watching this issue