[SERVER-2759] assertion failed ids not match Created: 15/Mar/11  Updated: 30/Mar/12  Resolved: 16/Mar/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 1.7.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: ofer samocha Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

pymongo 1.9


Operating System: ALL
Participants:

 Description   

got assertion failed ~30000 times and recover afterwards

Traceback (most recent call last):
File "dbconnector.py", line 32, in eval_cmd
res = eval_expr(block, variables)
File "dbconnector.py", line 25, in eval_expr
return eval(expr,

{"__builtins__":None}

, variables )
File "<string>", line 1, in <module>
File "dbmodules.py", line 232, in login
user = mdb.users.find_and_modify(query=

{USER_UDID:udid}

, update={"$set": {USER_VERSION:ClientVersion}})
File "build/bdist.linux-x86_64/egg/pymongo/collection.py", line 1061, in find_and_modify
allowable_errors=[no_obj_error], **kwargs)
File "build/bdist.linux-x86_64/egg/pymongo/database.py", line 288, in command
_is_command=True)
File "build/bdist.linux-x86_64/egg/pymongo/collection.py", line 469, in find_one
for result in self.find(spec_or_id, *args, **kwargs).limit(-1):
File "build/bdist.linux-x86_64/egg/pymongo/cursor.py", line 601, in next
if len(self.__data) or self._refresh():
File "build/bdist.linux-x86_64/egg/pymongo/cursor.py", line 564, in _refresh
self._query_spec(), self._fields))
File "build/bdist.linux-x86_64/egg/pymongo/cursor.py", line 521, in __send_message
**kwargs)
File "build/bdist.linux-x86_64/egg/pymongo/connection.py", line 790, in _send_message_with_response
return self.__send_and_receive(message, sock)
File "build/bdist.linux-x86_64/egg/pymongo/connection.py", line 771, in __send_and_receive
return self.__receive_message_on_socket(1, request_id, sock)
File "build/bdist.linux-x86_64/egg/pymongo/connection.py", line 761, in __receive_message_on_socket
struct.unpack("<i", header[8:12])[0])
AssertionError: ids don't match -1484018265 895640889



 Comments   
Comment by Eliot Horowitz (Inactive) [ 16/Mar/11 ]

This is likely a bug fixed since 1.7.6.
You should upgrade to 1.8.0-rc2 (or newer).
If it happens again with that version, please re-open with all log files from mongos and mongod

Comment by ofer samocha [ 16/Mar/11 ]

nothing there, sorry
errors were between 01:19 and 01:35

Tue Mar 15 01:19:57 [LockPinger] dist_lock pinged successfully for: SN13:1299669121:1804289383
Tue Mar 15 01:24:57 [LockPinger] dist_lock pinged successfully for: SN13:1299669121:1804289383
Tue Mar 15 01:29:57 [LockPinger] dist_lock pinged successfully for: SN13:1299669121:1804289383
Tue Mar 15 01:30:09 [mongosMain] connection accepted from 127.0.0.1:33555 #1979
Tue Mar 15 01:30:09 [conn1979] end connection 127.0.0.1:33555
Tue Mar 15 01:34:57 [LockPinger] dist_lock pinged successfully for: SN13:1299669121:1804289383
Tue Mar 15 01:36:04 [mongosMain] connection accepted from 127.0.0.1:44280 #1980
Tue Mar 15 01:36:09 [mongosMain] connection accepted from 127.0.0.1:44284 #1981
Tue Mar 15 01:36:10 [conn1922] end connection 127.0.0.1:42097
Tue Mar 15 01:39:58 [LockPinger] dist_lock pinged successfully for: SN13:1299669121:1804289383

Comment by Eliot Horowitz (Inactive) [ 16/Mar/11 ]

Any mongos where there is an error.

Comment by ofer samocha [ 16/Mar/11 ]

in that mongos there was nothing to send.
in other 20 mongos there was no such error.
I have 40*2 mongo shards do you need their logs ?

Comment by Eliot Horowitz (Inactive) [ 16/Mar/11 ]

Can you send server log from that time

Generated at Thu Feb 08 03:01:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.