[SERVER-31984] A migration will simply report "Data transfer error" when we have rich error details on the destination shard that are logged but not returned to the user Created: 15/Nov/17 Updated: 30/Oct/23 Resolved: 06/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Sharding 2017-12-18 | ||||
| Participants: | |||||
| Description |
Wherever we call MigrationDestinationManager::setStateFailWarn, we're logging detailed error messages on the destination shard, but not returning the error messages. No logic issue, but usability issue. |
| Comments |
| Comment by Githook User [ 06/Dec/17 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: (cherry picked from commit 12a08f2246b8ec195b9f97449d5717895197b7ee) |
| Comment by Githook User [ 06/Dec/17 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |