how to reconfigure galeria mysql cluster

[bbnlaccts acnts]

Hi
I have been running a 3 node basic mysql 5.6 galeria cluster.
node1,node2,node3
node3 ran out of space and hence mysql shutdown. this is noticed after seeing high i/o on the rest of the clusters.
Since it is passed many days, if i try to bring up the node3 it is failing with innodb error.
How can i reconfigure the whole cluster from the scratch again.
I can take a dowtime, copy the files across across 2 nodes and start from scratch again.
In order to achieve what needs to be done, how can I cleanup all the galeria cluster info,logs,quorumfiles etc. and build it again from the scratch.

Please do let me know the steps to be followed in order to reconfigure the galeria cluster across these 3 cluster nodes

Thanks in advance.
Arun

[Philip Stoev]

Hello,

Please provide the InnoDB error that you are getting when trying to start
node #3.

Philip Stoev

--
You received this message because you are subscribed to the Google Groups
"codership" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to codership-tea...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bbnlaccts acnts]

151005 07:08:08 mysqld_safe WSREP: Failed to recover position:  2015-10-05 07:07:48 29012 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2015-10-05 07:07:48 29012 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2015-10-05 07:07:48 29012 [Note] Plugin 'FEDERATED' is disabled. 2015-10-05 07:07:49 7ff3d298f740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2015-10-05 07:07:49 29012 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-10-05 07:07:49 29012 [Note] InnoDB: The InnoDB memory heap is disabled 2015-10-05 07:07:49 29012 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-10-05 07:07:49 29012 [Note] InnoDB: Memory barrier is not used 2015-10-05 07:07:49 29012 [Note] InnoDB: Compressed tables use zlib 1.2.3.4 2015-10-05 07:07:49 29012 [Note] InnoDB: Using Linux native AIO 2015-10-05 07:07:49 29012 [Note] InnoDB: Using CPU crc32 instructions 2015-10-05 07:07:49 29012 [Note] InnoDB: Initializing buffer pool, size = 3.0G 2015-10-05 07:08:00 29012 [Note] InnoDB: Completed initialization of buffer pool 2015-10-05 07:08:06 29012 [Note] InnoDB: Highest supported file format is Barracuda. 2015-10-05 07:08:06 29012 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1094878436501 2015-10-05 07:08:06 29012 [Note] InnoDB: Database was not shutdown normally! 2015-10-05 07:08:06 29012 [Note] InnoDB: Starting crash recovery. 2015-10-05 07:08:06 29012 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-10-05 07:08:08 29012 [Note] InnoDB: Restoring possible half-written data pages 2015-10-05 07:08:08 29012 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 1094880694416 01:38:08 UTC - 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=1073741824 read_buffer_size=131072 max_used_connections=0 max_threads=3000 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2243044 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 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8d02ee] /usr/sbin/mysqld(handle_fatal_signal+0x36a)[0x6584ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7ff3d190ccb0] /usr/sbin/mysqld[0x98c760] /usr/sbin/mysqld[0x98b627] /usr/sbin/mysqld[0x97280e] /usr/sbin/mysqld[0x973ce2] /usr/sbin/mysqld[0xa442bc] /usr/sbin/mysqld[0xa5650c] /usr/sbin/mysqld[0xa56e77] /usr/sbin/mysqld[0xa3ef3e] /usr/sbin/mysqld[0x9591e5] /usr/sbin/mysqld[0xa5a330] /usr/sbin/mysqld[0x9ec167] /usr/sbin/mysqld[0x92be17] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x59d348] /usr/sbin/mysqld[0x6e5416] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xda3)[0x6e7903] /usr/sbin/mysqld[0x5853b3] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x473)[0x5862c3] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7ff3d0f6476d] /usr/sbin/mysqld[0x5797fd] 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.