MySQL 5.7.17 + Galera3 では利用できない。
— Shinya Matsui 2017/04/10 17:52
新しいバージョンでバグが修正されるのを期待。(^^)
https://github.com/codership/mysql-wsrep/issues/298
# rpm -qa | grep mysql mysql-wsrep-client-5.7-5.7.17-25.10.20170117.92194e2.el6.x86_64 mysql-wsrep-libs-5.7-5.7.17-25.10.20170117.92194e2.el6.x86_64 mysql-wsrep-server-5.7-5.7.17-25.10.20170117.92194e2.el6.x86_64 mysql-wsrep-libs-compat-5.6-5.6.35-25.18.20170106.1f9ae89.el6.x86_64 mysql-wsrep-common-5.7-5.7.17-25.10.20170117.92194e2.el6.x86_64 # /etc/init.d/mysqld stop /usr/bin/mysqld_safe: line 1087: [: 1: unary operator expected Stopping mysqld: [ OK ] # tail /var/log/mysqld.log 2017-04-10T08:38:25.799325Z 0 [Note] Giving 5 client threads a chance to die gracefully 2017-04-10T08:38:25.799342Z 2 [Note] WSREP: applier thread exiting (code:0) 2017-04-10T08:38:25.809368Z 4 [Note] WSREP: applier thread exiting (code:6) 2017-04-10T08:38:25.809368Z 5 [Note] WSREP: applier thread exiting (code:6) 2017-04-10T08:38:25.809441Z 6 [Note] WSREP: applier thread exiting (code:6) pure virtual method called terminate called without an active exception 08:38:27 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=300 thread_count=1 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 127563 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... 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 stack_bottom = 0 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0xf6d725] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x7d5d34] /lib64/libpthread.so.0[0x366480f7e0] /lib64/libc.so.6(gsignal+0x35)[0x36644325e5] /lib64/libc.so.6(gsignal+0x35)[0x36644325e5] /lib64/libc.so.6(abort+0x175)[0x3664433dc5] /usr/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x12d)[0x36684bea7d] /usr/lib64/libstdc++.so.6[0x36684bcbd6] /usr/lib64/libstdc++.so.6[0x36684bcc03] /usr/lib64/libstdc++.so.6[0x36684bd55f] /usr/sbin/mysqld(_ZN18Global_THD_manager14do_for_all_thdEP11Do_THD_Impl+0x90)[0x7d4110] /usr/sbin/mysqld(_Z25wsrep_wait_appliers_closeP3THD+0x75)[0x7c6905] /usr/sbin/mysqld(_Z22wsrep_stop_replicationP3THD+0xb5)[0x7de1f5] /usr/sbin/mysqld(signal_hand+0x3a0)[0x7c9dc0] /usr/sbin/mysqld(pfs_spawn_thread+0x174)[0x126c244] /lib64/libpthread.so.0[0x3664807aa1] /lib64/libc.so.6(clone+0x6d)[0x36644e8aad] 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.