[SERVER-11124] mongos setShardVersion failed messages are cryptic Created: 10/Oct/13 Updated: 06/Dec/22 Resolved: 09/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | neweng, setShardVersionRemove | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In general, it takes a lot of sleuthing to figure out exactly which shard sent back a stale config error and why the shard was stale, in human-readable terms. This causes a disproportionate amount of support load, just figuring out what is actually wrong. We could change these messages to be much more descriptive: "shardXXX thinks the collection foo.bar is at a newer version XXX", etc. |