update record via sp kill cluster node
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Galera |
New
|
Undecided
|
Unassigned | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Won't Fix
|
Medium
|
Unassigned | |||
5.6 |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
HI,
i have a problem with percona mysql server. I have 3 node (VM with 4 core Intel processor, 7 GB RAM, GB Ethernet), ubuntu 12.04LTS with 5.5.30-30.2 Percona Server (GPL), Release 30.2, wsrep_23.7.4.r38. On this i have few DB, and problem is that database killed by my stored procedure. In store procedure i update some collumn in (innodb) table with 700k rows, and this update crash mysql node. SP is simple, like this:
PROCEDURE `proc_replace_
BEGIN
UPDATE table1
SET col1 = func(col1), col2 = func(col2)
END
where func is simple char replace function. By the way, when this procedure update table with 200k rows, procedure work ok, but with 700k rows procedure kill percona and i must restart server (no data change on table).
my.cnf:
#
# The MySQL database server configuration file.
#
[client]
port = 3306
socket = /var/run/
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/
socket = /var/run/
port = 3306
basedir = /usr
datadir = /mnt/data/mysql
tmpdir = /tmp/mysqltmp
language = /usr/share/
skip-external-
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = node1
binlog_format = ROW
######## Galera ########
# Full path to wsrep provider library or 'none' to disable galera
wsrep_provider = /usr/lib/
# set to "gcom://"" to reinitialise (reset) a node
#wsrep_
# once the nodes have mounted, we will set this to the floating ip
wsrep_cluster_
wsrep_cluster_
wsrep_node_name = mysql-node1
#### BOF : State Snapshot Transfer method
wsrep_sst_method = rsync
# alternative methods to-do SST
# experimental, wait for RC release
#wsrep_
# not recommended, transfers the ENTIRE database to re-sync nodes.
#wsrep_
# Set to number of cpu cores.
wsrep_slave_threads = 1
#### for MyISAM support
wsrep_replicate
####END of MyISAM
# to enable debug level logging, set this to 1
wsrep_debug = 1
# how many times to retry deadlocked autocommits
wsrep_retry_
# convert locking sessions into transactions
wsrep_convert_
# Generate fake primary keys for non-PK tables (required for multi-master and parallel applying operation)
wsrep_certify_nonPK = 1
#### Required for Galera
innodb_
innodb_
default_
query_cache_size = 0
query_cache_type = 0
######## EOF : Galera ########
#
# * Fine Tuning
#
key_buffer = 32M
max_allowed_packet = 32M
thread_stack = 192K
thread_cache_size = 8
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 32M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
general_log_file = /mnt/data/
general_log = 0
#
# Error logging goes to syslog due to /etc/mysql/
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/
#long_query_time = 2
#log-queries-
#
innodb_
innodb_
innodb_
federated
event_scheduler=ON
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
mysql-node1.err:
130514 11:29:14 [Note] WSREP: TO END: 1572149
130514 11:29:14 [Note] WSREP: TO BEGIN: 1572149, 0 : DROP FUNCTION `tmp_ems_proc_105`
130514 11:29:14 [Note] WSREP: TO BEGIN: 1572150, 2
130514 11:29:14 [Note] WSREP: TO END: 1572150, 2 : DROP FUNCTION `tmp_ems_proc_105`
130514 11:29:14 [Note] WSREP: TO END: 1572150
09:39:50 UTC - mysqld got signal 11 ;
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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=153
thread_count=5
connection_count=4
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: 0xa41a9b0
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 = 7fb424112e70 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/usr/lib/
/usr/lib/
/usr/lib/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fb2e40213d0): is an invalid pointer
Connection ID (thread ID): 45
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
130514 11:39:51 mysqld_safe Number of processes running now: 0
130514 11:39:51 mysqld_safe WSREP: not restarting wsrep node automatically
130514 11:39:51 mysqld_safe mysqld from pid file /var/run/
no longer affects: | percona-server |
If you do not see the problem on a non-cluster Percona Server, then this is more a Percona XtraDB Cluster problem it seems.