If you are hitting this regression with innodb_buffer_pool_populate, then you can do this:
--- mysqld_safe 2013-06-06 16:05:26.000000000 +0530 +++ /tmp/mysqld_safe 2013-06-07 15:27:54.660401912 +0530 @@ -222,7 +222,7 @@ log_notice "WSREP: Running position recovery with --log_error=$wr_logfile \ --pid-file="$DATADIR/`hostname`-recover.pid""
- eval_log_error "$mysqld_cmd --log_error=$wr_logfile --wsrep-recover \ + eval_log_error "$mysqld_cmd --log_error=$wr_logfile --innodb_buffer_pool_populate=0 --wsrep-recover \ --pid-file="$DATADIR/`hostname`-recover.pid""
local rp="$(grep 'WSREP: Recovered position:' $wr_logfile)"
If you are hitting this regression with innodb_ buffer_ pool_populate, then you can do this:
--- mysqld_safe 2013-06-06 16:05:26.000000000 +0530 $wr_logfile \
-- pid-file= "$DATADIR/ `hostname` -recover. pid""
+++ /tmp/mysqld_safe 2013-06-07 15:27:54.660401912 +0530
@@ -222,7 +222,7 @@
log_notice "WSREP: Running position recovery with --log_error=
- eval_log_error "$mysqld_cmd --log_error= $wr_logfile --wsrep-recover \ $wr_logfile --innodb_ buffer_ pool_populate= 0 --wsrep-recover \
--pid- file="$ DATADIR/ `hostname` -recover. pid""
+ eval_log_error "$mysqld_cmd --log_error=
local rp="$(grep 'WSREP: Recovered position:' $wr_logfile)"