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

_shardsvrDropCollectionParticipant with fromMigrate=true does not abort index builds

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.4, 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v6.2, v6.0
    • Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26
    • 140

      When dropping a collection, we abort any index builds on that collection before actually performing the drop. However, when the _shardsvrDropCollectionParticipant command is run with fromMigrate set to true (which currently is the case on all non-primary shards participating in the drop), this index build abort logic gets bypassed.

            Assignee:
            paolo.polato@mongodb.com Paolo Polato
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: