[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: |
|
||||||||||||||||
| 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.
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: |
| Comment by Lingzhi Deng [ 03/Feb/21 ] |
|
A potential solution is to use the mtab on recipient after |