MySQL Forums
Forum List  »  InnoDB

MySql Crash
Date: September 17, 2016 03:12AM

HI All,

I am running load test on mysql (with innodb and memcached) and got following error/crash

Version: '5.6.32-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)
mysqld: /export/home/pb2/build/sb_0-19672887-1468244967.53/release-ET46834/mysql-5.6.32/plugin/innodb_memcached/innodb_memcache/src/innodb_engine.c:1462: innodb_switch_mapping: Assertion `*name_len < 250' failed.
08:39:40 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76300 K bytes of memory
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
The manual page at contains
information that should help you find out what is causing the crash.
160917 08:39:41 mysqld_safe Number of processes running now: 0
160917 08:39:41 mysqld_safe mysqld restarted

Though the server restarted on its own, i still want to know the reason behind crash. At first, i was thinking the length of memcached table key's length may be a cause but i can not recreate crash when running queries with long key (> 250) . It only happen while running load test and mysql res memory > 4.7g.

Any help would be appriciated. If you need more logs/mysql conf please let me know here.


Options: ReplyQuote

Written By
MySql Crash
September 17, 2016 03:12AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.