[SERVER-13450] error message for moveChunk is confusing with incorrect shard key specified Created: 01/Apr/14 Updated: 06/Dec/22 Resolved: 03/Jan/19 |
|
| 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: | ShardingRoughEdges, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If the moveChunk "find" document does not contain a correct shard key, it may return:
...which is pretty cryptic. This is a pretty easy failure to detect and one that should be reported more clearly. |
| Comments |
| Comment by Kaloian Manassiev [ 03/Jan/19 ] |
|
The ChunkManager diagnostics and debugging messages have been significantly improved since 3.4 when the CatalogCache was re-written. |