[SERVER-52828] Add reason for migration abort in tenant migration abort response Created: 12/Nov/20 Updated: 27/Oct/23 Resolved: 01/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | pm-1791_non-cloud-blocking, pm-1791_polish | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
tomer.yakir requested that when a response indicates "state": "aborted" we should: |
| Comments |
| Comment by Jack Mulrow [ 01/Apr/21 ] |
|
Yeah I agree, the server should already have this behavior. I don't think we have a targeted test explicitly for this, but we already get coverage through a few other tests that assert on the abortReason in an aborted response (e.g. this one), so I think closing this is fine. |
| Comment by Lingzhi Deng [ 01/Apr/21 ] |
|
I think the donor already include the abortReason in its donorStartMigration response. The donor has this log line and the recipient has this. I think we probably don't need to do anything for this ticket. jack.mulrow what do you think? |