InnoDB: Assertion failure in thread 47550051727680 in file lock0lock.cc line 5579
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.5 |
New
|
Undecided
|
Unassigned | |||
| 5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
Bug Description
Server version: 5.6.15-rel63.0-log 5.6.15-, Percona XtraDB Cluster - binary (GPL), Release: 25.5, Revision 769 wsrep_25.5.r4061, wsrep_25.5.r40
download: Percona-
=====error.log=====
2014-05-05 16:04:53 17177 [Note] Shutting down plugin 'XTRADB_READ_VIEW'
2014-05-05 16:04:53 17177 [Note] Shutting down plugin 'InnoDB'
2014-05-05 16:04:53 17177 [Note] InnoDB: FTS optimize thread exiting.
2014-05-05 16:04:53 17177 [Note] InnoDB: Starting shutdown...
2014-05-05 16:04:53 2b3f1bf13940 InnoDB: Assertion failure in thread 47550051727680 in file lock0lock.cc line 5579
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.
08:04:53 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.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at https:/
key_buffer_
read_buffer_
max_used_
max_threads=1026
thread_count=0
connection_count=0
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: 0x0
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 = 0 thread_stack 0x40000
/home/abc/
/home/abc/
/lib64/
/lib64/
/lib64/
/home/abc/
/home/abc/
/home/abc/
/lib64/
/lib64/
You may download the Percona XtraDB Cluster operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
=======
# my.cnf
[client]
socket = /data/abc/
port = 3316
default-
[mysqld]
# [ 基本配置 ]
server-id = 1397720344
basedir = /home/abc/
datadir = /data/abc/data
user = abc
port = 3316
socket = /data/abc/
pid-file = /data/abc/
wait_timeout = 7200
net_retry_count = 100000000
thread_concurrency = 8
thread_stack = 256K
max_connections = 1024
max_connect_errors = 1024
open_files_limit = 4096
back_log = 1024
max_allowed_packet = 96M
auto_increment_
auto_increment_
default-
init_connect = 'SET NAMES utf8'
skip-name-resolve
explicit_
transaction-
# [ 扩展设置 ]
key_buffer_size = 16M
# table_open_cache =2000
# show global status like 'sort%';
# show global status like 'Created%';
sort_buffer_size = 4M
join_buffer_size = 2M
read_buffer_size = 4M
read_rnd_
myisam_
thread_cache_size = 2048
query_cache_limit = 8M
query_cache_
# show variables like '%query_cache%';
# show status like '%Qcache%';
query_cache_size = 512M
query_cache_type = ON
tmp_table_size = 2G
max_tmp_tables = 256
max_heap_table_size = 96M
bulk_insert_
# [ Galera 参数 ]
wsrep_node_name = abc_01
wsrep_node_address = 192.168.12.69
wsrep_provider = /home/abc/
wsrep_provider_
wsrep_sst_method = xtrabackup-v2
wsrep_sst_auth = sstuser:s3cretPass
wsrep_sst_
wsrep_cluster_name = abc
wsrep_slave_threads = 16
wsrep_cluster_
# [ binlog 参数 ]
binlog_format = ROW
log_slave_updates = 1
log-bin = /data/abc/
log-bin-index = /data/abc/
# 全局事务id，主从都是5.6才能开启
#enforce_
#gtid_mode = on
relay-log-index = /data/abc/
relay-log-info-file = /data/abc/
relay-log = /data/abc/
expire_logs_days = 30
binlog-ignore-db = mysql
binlog-ignore-db = test
binlog-ignore-db = dbsync
binlog-ignore-db = information_schema
replicate-ignore-db = mysql
replicate-ignore-db = test
replicate-ignore-db = dbsync
replicate-ignore-db = information_schema
binlog_cache_size = 64M
max_binlog_size = 128M
max_binlog_
max_relay_log_size = 256M
# [ 慢查询日志 ]
long_query_time = 0.3
log_slow_filter = qc_miss,
slow-query-log = 1
log_slow_verbosity = full
log-queries-
log-slow-
slow_query_log_file = /data/abc/
log-error = /data/abc/
# [ innodb 相关参数 ]
innodb_
innodb_
innodb_
innodb_
# 为了加速innodb 缓存的预热，关闭mysql时将
# 启动的时候再从磁盘载入到内存
innodb_
innodb_
# 每个表独立文件
innodb_
innodb_support_xa = 0
innodb_status_file = 1
# Innodb_
innodb_
innodb_
innodb_
innodb_
innodb_flush_method = 'O_DIRECT'
innodb_
innodb_
innodb_
innodb_
# 5.6.5 新增参数,默认是1
# 当刷新一个脏页时，
# 在区（extent）
# 进行刷新.
innodb_
[mysqldump]
quick
max_allowed_packet = 128M
| cooper (zyq916) wrote | #1 |
| information type: | Private Security → Public |
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #2 |
| cooper (zyq916) wrote | #3 |
| cooper (zyq916) wrote | #4 |
| h0rjulf (h0rjulf) wrote | #5 |
| infernix (infernix) wrote | #6 |
| Krastio Neshev (krastio) wrote | #7 |
| infernix (infernix) wrote | #8 |
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #9 |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #10 |
CentOS release 5.9 (Final) 2.6.18-348.el5 x86_64
CPU: E5-2630X2
MEM:64G