[SERVER-16360] exception during insert - caused by :: 16460 through mongos Created: 01/Dec/14 Updated: 07/Dec/14 Resolved: 07/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.7 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | temp123 | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows |
||
| Attachments: |
|
| Participants: |
| Description |
|
a component tried to insert a document and got an exception thanks in advance |
| Comments |
| Comment by Ramon Fernandez Marina [ 07/Dec/14 ] |
|
The description for error code 10053 says:
So mongos attempted an insert operation but that operation failed. mongos then asked the OS why, and the OS reported that a send() operation on a socket failed with error code 10053 (described above). The 16460 error code comes from MongoDB, and was logged when mongos detected that connection failure. Here's the relevant code block in mongos. Given the information above and the fact that it hasn't happened again I think this was just a network glitch, so I'm going to resolve this ticket. If the problem re-appears and starts happening often please feel free to re-open the ticket. Regards, |
| Comment by temp123 [ 07/Dec/14 ] |
|
hey Ramon, thank for your answer. this problem does not occurred ever since, but i am still not sure what is the source of this. |
| Comment by Ramon Fernandez Marina [ 05/Dec/14 ] |
|
According to the Windows Sockets Error Codes List it seems like the connection to the shard was aborted by the OS somehow. The 16460 code indicates an insert operation failed, in this case triggered by the network problem. Are you still seeing connectivity problems in your cluster? Is this a recurring problem? |