Crash of Percona XtraDB Cluster 5.6 node on UPDATE
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Crash of Percona XtraDB Cluster 5.6 node on UPDATE
Linux serv 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
percona-xtrabackup 2.1.8-733-1.wheezy amd64
percona-
percona-
percona-
percona-
Node permanently crashes on UPDATE query :
backtrace :
Apr 17 21:30:58 web177 mysqld: 2014-04-17 21:30:58 21598 [Note] WSREP: Created page /var/lib/
134217728 bytes
Apr 17 21:31:07 web177 mysqld: 18:31:07 UTC - mysqld got signal 6 ;
Apr 17 21:31:07 web177 mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 17 21:31:07 web177 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 17 21:31:07 web177 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 17 21:31:07 web177 mysqld: We will try our best to scrape up some info that will hopefully help
Apr 17 21:31:07 web177 mysqld: diagnose the problem, but since we have already crashed,
Apr 17 21:31:07 web177 mysqld: something is definitely wrong and this may fail.
Apr 17 21:31:07 web177 mysqld: Please help us make Percona XtraDB Cluster better by reporting any
Apr 17 21:31:07 web177 mysqld: bugs at https:/
Apr 17 21:31:07 web177 mysqld:
Apr 17 21:31:07 web177 mysqld: key_buffer_
Apr 17 21:31:07 web177 mysqld: read_buffer_
Apr 17 21:31:07 web177 mysqld: max_used_
Apr 17 21:31:07 web177 mysqld: max_threads=602
Apr 17 21:31:07 web177 mysqld: thread_count=69
Apr 17 21:31:07 web177 mysqld: connection_count=69
Apr 17 21:31:07 web177 mysqld: It is possible that mysqld could use up to
Apr 17 21:31:07 web177 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_
ry
Apr 17 21:31:07 web177 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 17 21:31:07 web177 mysqld:
Apr 17 21:31:07 web177 mysqld: Thread pointer: 0x7fab6c6d6f40
Apr 17 21:31:07 web177 mysqld: Attempting backtrace. You can use the following information to find out
Apr 17 21:31:07 web177 mysqld: where mysqld died. If you see no messages after this, something went
Apr 17 21:31:07 web177 mysqld: terribly wrong...
Apr 17 21:31:07 web177 mysqld: stack_bottom = 7fab88bafe30 thread_stack 0x30000
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /lib/x86_
Apr 17 21:31:07 web177 mysqld: /lib/x86_
Apr 17 21:31:07 web177 mysqld: /lib/x86_
Apr 17 21:31:07 web177 mysqld: /usr/lib/
7fac7d051645]
Apr 17 21:31:07 web177 mysqld: /usr/lib/
leEE+0xd1)
Apr 17 21:31:07 web177 mysqld: /usr/lib/
S3_13Certificat
Apr 17 21:31:07 web177 mysqld: /usr/lib/
Apr 17 21:31:07 web177 mysqld: /usr/lib/
056cae]
Apr 17 21:31:07 web177 mysqld: /usr/lib/
Apr 17 21:31:07 web177 mysqld: /usr/lib/
Apr 17 21:31:07 web177 mysqld: /usr/lib/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /usr/sbin/
Apr 17 21:31:07 web177 mysqld: /lib/x86_
Apr 17 21:31:07 web177 mysqld: /lib/x86_
Apr 17 21:31:07 web177 mysqld:
Apr 17 21:31:07 web177 mysqld: Trying to get some variables.
Apr 17 21:31:07 web177 mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 17 21:31:07 web177 mysqld: Query (9706530): UPDATE n5chk2_k2_items
Apr 17 21:31:07 web177 mysqld: SET `hits` = (`hits` + 1)
Apr 17 21:31:07 web177 mysqld: WHERE `id` = '336616'
Apr 17 21:31:07 web177 mysqld: Connection ID (thread ID): 55272
Apr 17 21:31:07 web177 mysqld: Status: NOT_KILLED
Apr 17 21:31:07 web177 mysqld:
Apr 17 21:31:07 web177 mysqld: You may download the Percona XtraDB Cluster operations manual by visiting
Apr 17 21:31:07 web177 mysqld: http://
Apr 17 21:31:07 web177 mysqld: in the manual which will help you identify the cause of the crash.
Apr 17 21:31:07 web177 mysqld_safe: Number of processes running now: 0
Apr 17 21:31:07 web177 mysqld_safe: WSREP: not restarting wsrep node automatically
Apr 17 21:31:07 web177 mysqld_safe: mysqld from pid file /var/run/
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXC-1668