Failing assertion: !rec_get_deleted_flag(rec, rec_offs_comp(offsets)) with debug 5.5 build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
New
|
Undecided
|
Unassigned |
Bug Description
Standard seesaw test yielded on donor (debug build form 5.5 branch head):
130825 13:07:25 [Note] WSREP: Quorum results:
version = 2,
component = PRIMARY,
conf_id = 5,
members = 2/3 (joined/total),
act_id = 3675,
last_appl. = 3552,
protocols = 0/4/2 (gcs/repl/appl),
group UUID = bcabf528-
130825 13:07:25 [Note] WSREP: Flow-control interval: [28, 28]
130825 13:07:25 [Note] WSREP: New cluster view: global state: bcabf528-
130825 13:07:25 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
130825 13:07:25 [Note] WSREP: Assign initial position for certification: 3675, protocol version: 2
130825 13:07:26 InnoDB: Assertion failure in thread 140337117845248 in file row0sel.c line 2724
InnoDB: Failing assertion: !rec_get_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
10:07:26 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_
read_buffer_
max_used_
max_threads=1024
thread_count=13
connection_count=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x20121c0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fa2c80ece50 thread_stack 0x40000
/run/shm/
/run/shm/
/lib/x86_
/lib/x86_
/lib/x86_
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa270004bc0): SELECT * FROM comm02 WHERE p = 2
Connection ID (thread ID): 27
Status: NOT_KILLED
Never had this before, DONOR status is probably not essential - state request hasn't been processed yet.
Was the innodb_flush_method set to O_DIRECT when this happened? I
noticed this crash only when it was set to default. Since
O_DIRECT is used normally, I didn't decide to pursue it further.
Also, I noticed this only on jenkins with VMs, so not having
O_DIRECT indicated to some issue with VM caching.