Quantcast
Channel: MySQL Forums - InnoDB
Viewing all articles
Browse latest Browse all 1957

mysqld 5.6 crash with daemon_memcached_w_batch_size > 1 (1 reply)

$
0
0
Hello,

I am testing the new innodb-memcached functionnality (MySQL 5.6.9-rc) on a debian squeeze system.

Setting data to my innodb table is working well with memcached PHP api.

But as soon as I set daemon_memcached_w_batch_size=2 (defaults to 1) in the mysql config file (my.cnf), mysqld crashes on memcache set.

My simple test script (php) :

$memcache = new Memcached();
// ...
$memcache->set('myKey1', 'value 1');
$memcache->set('myKey2', 'value 2);

=> crash on the second set (because of daemon_memcached_w_batch_size=2)

Note : it works with daemon_memcached_w_batch_size=1


Any similar experience ?


Here is the backtrace :

-----

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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=2
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76407 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 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x8edc75]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3e8)[0x66a6e8]
/lib/libpthread.so.0(+0xeff0)[0x7fa320f95ff0]
/usr/local/mysql/bin/mysqld[0x9c26ce]
/usr/local/mysql/bin/mysqld[0x9c34de]
/usr/local/mysql/bin/mysqld[0xa24433]
/usr/local/mysql/bin/mysqld[0xa34055]
/usr/local/mysql/bin/mysqld[0xa3435b]
/usr/local/mysql/lib/plugin//innodb_engine.so(innodb_api_begin+0x100)[0x7fa307165560]
/usr/local/mysql/lib/plugin//innodb_engine.so(+0x7dbd)[0x7fa307162dbd]
/usr/local/mysql/lib/plugin//innodb_engine.so(+0x8c53)[0x7fa307163c53]
/usr/local/mysql/lib/plugin/libmemcached.so(conn_nread+0xec7)[0x7fa31a2c4ac7]
/usr/local/mysql/lib/plugin/libmemcached.so(+0xb54e)[0x7fa31a2b954e]
/usr/local/mysql/lib/plugin/libmemcached.so(event_base_loop+0x379)[0x7fa31a2c95e9]
/usr/local/mysql/lib/plugin/libmemcached.so(+0x18ea2)[0x7fa31a2c6ea2]
/lib/libpthread.so.0(+0x68ca)[0x7fa320f8d8ca]
/lib/libc.so.6(clone+0x6d)[0x7fa31fd04b6d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130129 15:41:26 mysqld_safe Number of processes running now: 0
130129 15:41:26 mysqld_safe mysqld restarted
2013-01-29 15:41:26 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-01-29 15:41:26 29193 [Note] Plugin 'FEDERATED' is disabled.
2013-01-29 15:41:26 29193 [Note] InnoDB: The InnoDB memory heap is disabled
2013-01-29 15:41:26 29193 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-01-29 15:41:26 29193 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-01-29 15:41:26 29193 [Note] InnoDB: CPU does not support crc32 instructions
2013-01-29 15:41:26 29193 [Note] InnoDB: Using Linux native AIO
2013-01-29 15:41:26 29193 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-01-29 15:41:26 29193 [Note] InnoDB: Completed initialization of buffer pool
2013-01-29 15:41:26 29193 [Note] InnoDB: Highest supported file format is Barracuda.
2013-01-29 15:41:26 29193 [Note] InnoDB: Log scan progressed past the checkpoint lsn 40381758
2013-01-29 15:41:26 29193 [Note] InnoDB: Database was not shutdown normally!
2013-01-29 15:41:26 29193 [Note] InnoDB: Starting crash recovery.
2013-01-29 15:41:26 29193 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-01-29 15:41:26 29193 [Note] InnoDB: Restoring possible half-written data pages
2013-01-29 15:41:26 29193 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 40381765
InnoDB: Last MySQL binlog file position 0 555, file name mysql-bin.000024
2013-01-29 15:41:26 29193 [Note] InnoDB: 128 rollback segment(s) are active.
2013-01-29 15:41:26 29193 [Note] InnoDB: Waiting for purge to start
2013-01-29 15:41:26 29193 [Note] InnoDB: 1.2.9 started; log sequence number 40381765
2013-01-29 15:41:26 29193 [Note] Server hostname (bind-address): '*'; port: 3306
2013-01-29 15:41:26 29193 [Note] IPv6 is available.
2013-01-29 15:41:26 29193 [Note] - '::' resolves to '::';
2013-01-29 15:41:26 29193 [Note] Server socket created on IP: '::'.
2013-01-29 15:41:26 29193 [Note] Event Scheduler: Loaded 0 events
2013-01-29 15:41:26 29193 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.9-rc' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)


-----
Regards,
Nico

Viewing all articles
Browse latest Browse all 1957

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>