Not the answer you need?
Register and ask your own question!

InnoDB crashing on high usage - mysqldump...???

xman123xman123 EntrantCurrent User Role Beginner
Hi,
I moving all my websites from my old server to new dell dual E5-2620 v3 server with 32GB ddr4 RAM and 850 pro ssd for percona DB (5.5.46-37.6), CENTOS 6.7 x86_64, cPanel, all working fine but under high load like normal DB queries + backup (mysqldump) for some reason InnoDB`s randomly crashing, here is one example in error log:

mysqld got signal 6 ;
70This 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.
edWe 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://bugs.percona.com/

19key_buffer_size=2306867200
eeread_buffer_size=2097152
69max_used_connections=801
e9max_threads=802
13thread_count=110
a7connection_count=110
83It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10475236 K bytes of memory
a3Hope that's ok; if not, decrease some variables in the equation.

d9Thread pointer: 0x0
9bAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...

InnoDB: End of page dump
151207 2:51:24 InnoDB: Page checksum 1020940280 (32bit_calc: 326569872), prior-to-4.0.14-form checksum 3497737457
InnoDB: stored checksum 3981144642, prior-to-4.0.14-form stored checksum 3086526026
InnoDB: Page lsn 12 2130429837, low 4 bytes of lsn at page end 931869155
InnoDB: Page number (if stored to page already) 442440,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 27
InnoDB: Page may be an index page where index id is 81
InnoDB: (index "PRIMARY" of table "db"."links")
InnoDB: Page directory corruption: supremum not pointed to

Here is my.cnf:

[mysqldump]
max_allowed_packet=16M
quick
[mysqld]
default-storage-engine=MyISAM
innodb_file_per_table=1
log-warnings=1
open_files_limit=31174
innodb_log_file_size=128M
sort_buffer_size=8M
skip-name-resolv
open-files-limit=150000
max_connections=800
query_cache_limit=30M
# safe-show-database
connect_timeout=10
query_cache_size=0M
#query_cache_size=0
max_allowed_packet=268435456
query_cache_min_res_unit=2K
tmp_table_size=3800M
key_buffer_size=2200M
#thread_concurrency=16
read_rnd_buffer_size=2M
join_buffer_size=8M
query_prealloc_size=16384
skip-external-locking
#query_cache_type=1
query_cache_type=0
innodb_flush_method=O_DIRECT
innodb_buffer_pool_size=8000M
innodb_thread_concurrency=0
innodb_read_io_threads=64
innodb_write_io_threads=64
innodb_stats_on_metadata=0
innodb_io_capacity=1500
innodb_buffer_pool_instances=8
innodb_adaptive_flushing_method=keep_average
read_buffer_size=2M
table_cache=20000
wait_timeout=30
query_alloc_block_size=16384
tmpdir="/var/lib/mysql/tmp"
log-slow-queries="/var/log/mysql-slow.log"
ft_min_word_len=2
max_heap_table_size=3800M
myisam_sort_buffer_size=200M
max_connect_errors=100000
thread_cache_size=600
table_definition_cache=15000
skip-external-locking
myisam_max_sort_file_size=8000M
myisam_repair_threads=6
[myisamchk]
key_buffer=256M
write_buffer=64M
read_buffer=64M
sort_buffer=256M
[mysqld_safe]


I can`t find nothing else in logs on server and I can`t find where is problem, I try to backup -> drop -> restore some of tables but that don`t help because InnoDB`s randomly crashing...also sometimes it crash if I try to restore some big table (timeout)...

Also, I must say that I already asked from my host to swap the RAM and they do it but that don`t fix problem....now I thinking about RAID controller ( MegaRAID SAS-3 3108 + PERC H730 ) and I asked from my host to plug hard drives directly to MB because I don`t using RAID but they said that it not possible because RAID controller is embedded....

What you thinking, where can be problem?

​Thanks.

Comments

  • xman123xman123 Entrant Current User Role Beginner
    Look, I don`t have any warning about memory usage or something like that...also, tables crashing randomly and I don`t know what to do...most of that tables are few GB size and all of them InnoDB...
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.