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

Block TTL deletions on tenant being migrated on recipient until the migration is forgotten

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Sharding 2021-03-08, Sharding 2021-03-22

      The donor should already block TTL deletions once it enters the blocking phase. But the recipient could do TTL deletions independent of the donor. This could be an issue in the following sequence.

      1. donor receives update to _id:1 to so no longer matches ttl
      2. recipient ttl deletes _id:1 independently due to ttl
      3. recipient receives op='u' and ignores it

      So we should block TTL deletions on recipient for collections being migrated until the migration is done (marked as garbage collectable).

            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            lingzhi.deng@mongodb.com Lingzhi Deng
            0 Vote for this issue
            4 Start watching this issue