[SERVER-10716] Misleading error message when chunk has too many documents to move Created: 09/Sep/13 Updated: 06/Dec/22 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
In the error message, we say "can't move chunk of size (approximately) ... because maximum size allowed to move is ...", but the actual error may be that there are too many records, not that the chunk is too big. |
| Comments |
| Comment by Kaloian Manassiev [ 06/Sep/18 ] |
|
With the recent changes to chunk migration (starting in 3.4) the message has been made more descriptive. |