[SERVER-69235] Remove TTL index on tenant migration recipient state document namespace Created: 29/Aug/22 Updated: 29/Oct/23 Resolved: 27/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Serverless
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Service Arch 2023-07-24, Service Arch 2023-08-07 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
This ticket should stop calling createIndexes for the TTL index in TenantMigrationRecipientService::_rebuildService, and should instead call dropIndexes there to drop the TTL index if it exists because an earlier deployment was upgraded to the newer binaries. This ticket should also add an upgrade/downgrade test under jstests/multiVersion that an existing TTL index gets deleted on upgrade. |
| Comments |
| Comment by Githook User [ 27/Jul/23 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |
| Comment by Suganthi Mani [ 03/Jul/23 ] |
|
Both SERVER-69236 & Both donor and recipient creates external key collection with ttl index, for storing signing keys. I don't recall why we need ttl index for the external key collection and if it can be cleaned in-line by the instance run() method. In either case, any work for external key collection, can be done as a separate ticket by Serverless team and shouldn't affect SERVER-61717. |
| Comment by Suganthi Mani [ 29/Jun/23 ] |
|
We might need to fix this as after SERVER-61717 can cause some evergreen noises. so reopening this ticket and flagging for scheduling. |
| Comment by Didier Nadeau [ 21/Apr/23 ] |
|
Tenant Migration recipient code is not used by Shard Merge anymore. As we're sunsetting Tenant Migration, the code will be removed and we don't need to invest time to remove the TTL. |