[SERVER-13571] reproduceable mongodump crash on special collection Created: 14/Apr/14 Updated: 10/Dec/14 Resolved: 25/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Max Quatember | Assignee: | J Rassi |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Windows |
| Participants: |
| Description |
|
Hi Everyone! I have a reproduceable crash with latest mongodump on windows 8.1. Behaviour:
I attached the logfiles of mongod+mongodump, both started with "-vvv". Thanks for the help! BR, |
| Comments |
| Comment by J Rassi [ 25/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm resolving this ticket as "Can't reproduce". Tentative diagnosis is that a networking misconfiguration is causing the OS to close the server's connection to the client, and that this behavior manifests when the socket buffer is filled up on the sender side by the "exhaust cursor" feature; further diagnosis is out of scope of this ticket (for further research, note that a Windows network trace may reveal the system event that triggers the connection teardown – see netsh trace start help). Please re-open this ticket if you encounter the problem on a different machine. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Quatember [ 18/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Jason! Your python script said following:
I now tested the same dump on an other machine that is similar (Hardware, OS, Config) to mine. There everything worked. Thank you for your quick help, I hope I was not too annoying BR, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 17/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
My mistake, I did not realize that the shell does not support the "exhaust" query option. PyMongo (the MongoDB driver for Python) does support this query option; do you have Python installed on this machine? If so, could you provide the output of running the following line at the Python prompt? It runs the PyMongo equivalent of the shell snippet I sent above. See the PyMongo homepage for installation instructions (MS installer direct download link here, assuming you are using Python 2.7).
I suspect that the root cause of the issue is a networking misconfiguration on the host machine, evidenced by the following snippet from the 2.6.0 mongod log. The server received socket error WSAECONNABORTED (errno 10053) when trying to write to the client over the network connection.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Quatember [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Jason! Problem is reproduceable with the "Day" collection only. With 2.4.8 and 2.6.0. The result of your query:
BR, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
And, I have one more query to ask you to test running at the mongo shell, if you would (adds the "Exhaust cursor" query option, which mongodump also uses):
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Can you confirm that you used options "-d db -c Day" during this trial mongodump run, and that it was unsuccessful? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Quatember [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Jason! Output of the mongoshell:
The logfiles will follow soon... BR, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Could you paste the output of running the following at the mongo shell? The last line emulates the query that mongodump is running.
In addition, would you be willing to download MongoDB 2.6.0 (available here) and upload the new mongodump and mongod logs (both with log level 3) generated when you attempt to dump the same collection? MongoDB 2.6.0 outputs additional debugging information at this log level. Thanks. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Quatember [ 14/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Matt! I'm ready! What do I have to do? BR, |