[SERVER-55466] Run ping command at end of tenant migration txn passthrough tests Created: 23/Mar/21 Updated: 29/Oct/23 Resolved: 19/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 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: |
v5.0, v4.9
|
||||
| Sprint: | Repl 2021-04-05, Repl 2021-05-17, Repl 2021-05-31 | ||||
| Participants: | |||||
| Description |
|
In tenant migrations, I'm seeing this sequence of events:
In this case, should the donor transactions be cleaned up automatically? Or do we want users to manually issue a commitTransaction or abortTransaction to clean up these transactions? Another open question: If we do want to automatically clean up these transactions on the donor, should we still do this if the migration fails? |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 25/May/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: (cherry picked from commit 8fe57ad3781e3d261fd904d2e9b282c668889efc) |
| Comment by Githook User [ 19/May/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |