[SERVER-55236] Test retrying session migration after a failed tenant migration Created: 16/Mar/21 Updated: 29/Oct/23 Resolved: 05/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0-rc1, 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-H, pm-1791_non-cloud-blocking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.9
|
||||||||||||
| Sprint: | Repl 2021-04-05, Repl 2021-04-19 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
After a failed tenant migration, we expect Cloud to clean up tenant data. But the config.transactons entries that were migrated as part of the failed migration are not cleaned up. We should write a test that involves both retryable writes and transactions to test that retrying the config.transactions migration after a failed tenant migration works. |
| Comments |
| Comment by Githook User [ 05/Apr/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |
| Comment by Githook User [ 05/Apr/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: (cherry picked from commit 5ced636afebd2b07a4ad65ce2367667733715bd2) |
| Comment by Githook User [ 05/Apr/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |