[SERVER-6134] stale mongod view of shards causes m/r error Created: 19/Jun/12 Updated: 06/Dec/22 Resolved: 21/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce, Sharding |
| Affects Version/s: | 2.0.6, 2.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If a shard is removed during the M/R process, due to 2.1.2 improves the error message but does not fully solve. There isn't a way currently to manually refresh the shard view aside from triggering a migration (only in 2.1.2). Better messaging should be put around socket exceptions due to |
| Comments |
| Comment by Greg Studer [ 19/Jun/12 ] |
|
Only currently known 2.0 workaround is to cycle the shard primary and restart the previous primary while secondary. |