[SERVER-14967] Migrations are aborted after step2 without a logged reason Created: 20/Aug/14 Updated: 25/Jun/15 Resolved: 13/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging, Sharding |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
If a particular shard misses the shard key index, any migrations from it will fail, which is expected. What is unexpected, is that no explicit error is logged even with loglevel 1, basically leaving the operator guessing what's wrong. |
| Comments |
| Comment by Greg Studer [ 13/Nov/14 ] |
|
Issue is fixed by |