[SERVER-53768] Block TTL deletions on tenant being migrated on recipient until the migration is forgotten Created: 13/Jan/21  Updated: 29/Oct/23  Resolved: 15/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Andrew Shuvalov (Inactive)
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-B
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-54920 Move the tenant migration recipient M... Closed
Related
related to SERVER-53582 Create and remove TenantMigrationAcce... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-03-08, Sharding 2021-03-22
Participants:

 Description   

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).



 Comments   
Comment by Githook User [ 15/Mar/21 ]

Author:

{'name': 'Andrew Shuvalov', 'email': 'andrew.shuvalov@mongodb.com', 'username': 'shuvalov-mdb'}

Message: SERVER-53768: Block TTL deletions on tenant being migrated on recipient until the migration is forgotten
Branch: master
https://github.com/mongodb/mongo/commit/93e67c74e31dcd40965d3ad138ce4f5657a72265

Comment by Lingzhi Deng [ 03/Feb/21 ]

A potential solution is to use the mtab on recipient after SERVER-53582.

Generated at Thu Feb 08 05:31:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.