2014-01-17 08:36:10 |
Ales Perme |
description |
We operate Percona XtraDB cluster of three servers version: 5.5.34-31.1, Percona XtraDB Cluster (GPL), Release 31.1, wsrep_25.9.r3928
On a database having table with following structure:
CREATE TABLE `docStatsDetail` (
`date` date NOT NULL,
`adId` varchar(36) COLLATE utf8_slovenian_ci NOT NULL,
`userId` varchar(100) COLLATE utf8_slovenian_ci DEFAULT NULL,
`adImpressions` int(11) DEFAULT '0',
`adClicks` int(11) DEFAULT '0',
`ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`date`,`adId`),
KEY `TS` (`ts`),
KEY `_adId` (`adId`),
KEY `_userId` (`userId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_slovenian_ci;
The table has 120 mio records and if we try to delete from this table more than 20 mio records using: DELETE FROM docStatsDetail LIMIT 20000000; the server crashes with a crash report:
10:57:55 UTC - mysqld got signal 7 ;
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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=14
max_threads=102
thread_count=10
connection_count=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759054 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x5b7cdb0
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 = 7f31a953ae70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7e5c1e]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6bb5a4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f3266e54cb0]
/lib/x86_64-linux-gnu/libc.so.6(+0x14fecd)[0x7f326659becd]
/usr/lib/libgalera_smm.so(_ZN6galera12MappedBuffer7reserveEm+0x263)[0x7f3264b33fa3]
/usr/lib/libgalera_smm.so(_ZN6galera12MappedBuffer6resizeEm+0x19)[0x7f3264b34369]
/usr/lib/libgalera_smm.so(_ZN6galera9TrxHandle5flushEm+0xb5)[0x7f3264b5ce65]
/usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM9replicateEPNS_9TrxHandleEP14wsrep_trx_meta+0xd7)[0x7f3264b72537]
/usr/lib/libgalera_smm.so(galera_pre_commit+0xbb)[0x7f3264b88eeb]
/usr/sbin/mysqld(_Z22wsrep_run_wsrep_commitP3THDP10handlertonb+0xadf)[0x66cf9f]
/usr/sbin/mysqld[0x66db3b]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x2f5)[0x6be3d5]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x29)[0x662489]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x77c)[0x5ac7bc]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x314)[0x5b4534]
/usr/sbin/mysqld[0x5b4e58]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2502)[0x5b7972]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x167)[0x5b80f7]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x65490f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x654ae1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f3266e4ce9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f32665403fd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f317c004b90): is an invalid pointer
Connection ID (thread ID): 48
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
140116 11:57:55 mysqld_safe Number of processes running now: 0
140116 11:57:55 mysqld_safe WSREP: not restarting wsrep node automatically
140116 11:57:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
The servers have following settings:
# ------------------------------------------------------------
# wsrep provider configuration: basic wsrep options
# ------------------------------------------------------------
wsrep_on = 1
wsrep_debug = 0
wsrep_provider = /usr/lib/libgalera_smm.so
wsrep_provider_options = "gcache.size=16G;gcache.page_size=512M;"
# Empty gcomm address is being used when cluster is getting bootstrapped. Dont use it later. It will form new cluster!!!
#wsrep_cluster_address = gcomm://
wsrep_cluster_address = gcomm://ae-01
wsrep_cluster_name = bolha_cluster
wsrep_node_name = as-02.bolha.com
wsrep_node_address = ae-02
wsrep_sst_method = xtrabackup-v2
wsrep_sst_auth = "sstuser:miniklik3699"
wsrep_slave_threads = 8
wsrep_notify_cmd = /etc/mysql/wsrep_notify
# Dodal aAP
wsrep_max_ws_rows = 128K
wsrep_max_ws_size = 4096M
# ------------------------------------------------------------
# InnoDB
# ------------------------------------------------------------
innodb_log_file_size = 4096M
innodb_log_files_in_group = 4
innodb_buffer_pool_size = 1024M
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 256M
innodb_file_per_table = 1
innodb_open_files = 131072
innodb_io_capacity = 1000
innodb_flush_method = O_DIRECT
# dodal AP
innodb_adaptive_flushing_method = keep_average
innodb_flush_neighbor_pages = none
innodb_max_dirty_pages_pct = 60
innodb_read_io_threads = 8
innodb_write_io_threads = 8
Servers are running on SSD's and the erorr is reproducable in every node.
Servers are Linux based
Linux XXX 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise
PLEASE HELP! |
We operate Percona XtraDB cluster of three servers version: 5.5.34-31.1, Percona XtraDB Cluster (GPL), Release 31.1, wsrep_25.9.r3928
On a database having table with following structure:
CREATE TABLE `docStatsDetail` (
`date` date NOT NULL,
`adId` varchar(36) COLLATE utf8_slovenian_ci NOT NULL,
`userId` varchar(100) COLLATE utf8_slovenian_ci DEFAULT NULL,
`adImpressions` int(11) DEFAULT '0',
`adClicks` int(11) DEFAULT '0',
`ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`date`,`adId`),
KEY `TS` (`ts`),
KEY `_adId` (`adId`),
KEY `_userId` (`userId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_slovenian_ci;
The table has 120 mio records and if we try to delete from this table more than 20 mio records using: DELETE FROM docStatsDetail LIMIT 20000000; the server crashes with a crash report:
10:57:55 UTC - mysqld got signal 7 ;
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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=14
max_threads=102
thread_count=10
connection_count=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759054 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x5b7cdb0
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 = 7f31a953ae70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7e5c1e]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6bb5a4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f3266e54cb0]
/lib/x86_64-linux-gnu/libc.so.6(+0x14fecd)[0x7f326659becd]
/usr/lib/libgalera_smm.so(_ZN6galera12MappedBuffer7reserveEm+0x263)[0x7f3264b33fa3]
/usr/lib/libgalera_smm.so(_ZN6galera12MappedBuffer6resizeEm+0x19)[0x7f3264b34369]
/usr/lib/libgalera_smm.so(_ZN6galera9TrxHandle5flushEm+0xb5)[0x7f3264b5ce65]
/usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM9replicateEPNS_9TrxHandleEP14wsrep_trx_meta+0xd7)[0x7f3264b72537]
/usr/lib/libgalera_smm.so(galera_pre_commit+0xbb)[0x7f3264b88eeb]
/usr/sbin/mysqld(_Z22wsrep_run_wsrep_commitP3THDP10handlertonb+0xadf)[0x66cf9f]
/usr/sbin/mysqld[0x66db3b]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x2f5)[0x6be3d5]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x29)[0x662489]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x77c)[0x5ac7bc]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x314)[0x5b4534]
/usr/sbin/mysqld[0x5b4e58]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2502)[0x5b7972]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x167)[0x5b80f7]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x65490f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x654ae1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f3266e4ce9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f32665403fd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f317c004b90): is an invalid pointer
Connection ID (thread ID): 48
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
140116 11:57:55 mysqld_safe Number of processes running now: 0
140116 11:57:55 mysqld_safe WSREP: not restarting wsrep node automatically
140116 11:57:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
The servers have following settings:
# ------------------------------------------------------------
# wsrep provider configuration: basic wsrep options
# ------------------------------------------------------------
wsrep_on = 1
wsrep_debug = 0
wsrep_provider = /usr/lib/libgalera_smm.so
wsrep_provider_options = "gcache.size=16G;gcache.page_size=512M;"
# Empty gcomm address is being used when cluster is getting bootstrapped. Dont use it later. It will form new cluster!!!
#wsrep_cluster_address = gcomm://
wsrep_cluster_address = gcomm://ae-01
wsrep_cluster_name = bolha_cluster
wsrep_node_name = as-02.bolha.com
wsrep_node_address = ae-02
wsrep_sst_method = xtrabackup-v2
wsrep_sst_auth = "sstuser:mXXXXXX9"
wsrep_slave_threads = 8
wsrep_notify_cmd = /etc/mysql/wsrep_notify
# Dodal aAP
wsrep_max_ws_rows = 128K
wsrep_max_ws_size = 4096M
# ------------------------------------------------------------
# InnoDB
# ------------------------------------------------------------
innodb_log_file_size = 4096M
innodb_log_files_in_group = 4
innodb_buffer_pool_size = 1024M
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 256M
innodb_file_per_table = 1
innodb_open_files = 131072
innodb_io_capacity = 1000
innodb_flush_method = O_DIRECT
# dodal AP
innodb_adaptive_flushing_method = keep_average
innodb_flush_neighbor_pages = none
innodb_max_dirty_pages_pct = 60
innodb_read_io_threads = 8
innodb_write_io_threads = 8
Servers are running on SSD's and the erorr is reproducable in every node.
Servers are Linux based
Linux XXX 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise
PLEASE HELP! |
|