-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:MongoDb version 2.4.1 on a CentOS 6.0
-
Linux
-
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I'm streaming data in to the MongoDB on a socket using the MongoDB Wire Protocol. It seems like the DB lose the synchronisme, and I have to close and re-open the socket. This happen about every 2000 record I try to insert.
I get the following types of errors in the log:
19:26:27.129 [initandlisten] connection accepted from 10.190.35.153:57149 #1729 (2 connections now open)
19:26:27.629 [initandlisten] connection accepted from 10.190.35.153:57150 #1730 (3 connections now open)
19:26:59.319 [conn1729] Assertion: 10307:Client Error: bad object in message: bson length doesn't match what we found
19:26:59.322 [conn1729] insert cdr.things keyUpdates:0 exception: Client Error: bad object in message: bson length doesn't match what we found code:10307 0ms
19:26:59.322 [conn1729] recv(): message len 959525686 is too large. Max is 48000000
19:26:59.322 [conn1729] end connection 10.190.35.153:57149 (2 connections now open)
19:27:28.660 [initandlisten] connection accepted from 10.190.35.153:57153 #1733 (3 connections now open)
19:27:29.184 [conn1733] OpCounters::gotOp unknown op: 26740
19:27:29.184 [conn1733] Assertion: 16141:cannot translate opcode 26740
19:27:29.187 [conn1733] AssertionException handling request, closing client connection: 16141 cannot translate opcode 26740