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

Execute the kDropCollection phase of dropCollection under a RecoverableCriticalSection

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
    • 153

      DropCollectionCoordinator is currently deleting the collection metadata and data without explicitly blocking any user write operation on the namespace. While this behaviour is aligned with the isolation guarantees offered by the DDL, it may lead to an inconsistent sequence of events in the primary shard oplog.

      The addition of a RecoverableCriticalSection protecting the execution of the whole kDropCollection phase could be a way to solve this problem.

            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            paolo.polato@mongodb.com Paolo Polato
            0 Vote for this issue
            4 Start watching this issue