[SERVER-27515] Issue with sharding a huge collection(splitVector timeout) Created: 26/Dec/16 Updated: 16/Jan/17 Resolved: 12/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suraj Sawant | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Hi,
While inspecting logs,We have found that splitVector command is timing out.
Collection Details: Collection Stats file is also attached for details about collection. Have attached all possibly required logs by setting log verbose level to 2. We have gone through following link. It suggests to dump the data out and re-import it. |
| Comments |
| Comment by Suraj Sawant [ 16/Jan/17 ] |
|
Hi Kaloian, I will upgrade the version to 3.2.10 or later and will check. Suraj |
| Comment by Kaloian Manassiev [ 12/Jan/17 ] |
|
This problem is caused by mongos erroneously using a 30 second timeout when talking to shards and has been fixed as part of If you update to that version (or later) you should not be seeing this problem anymore. Best regards, |