PXC 5.5.30-23.7.4.404 not able the use a different shared memory allocator library

Yes, the wsrep_recovery needs eval_log_error:

diff -u =mysqld_safe /tmp/mysqld_safe
--- /usr/bin/mysqld_safe 2013-04-18 18:48:27.595069642 +0530
+++ /tmp/mysqld_safe 2013-04-18 18:45:55.539099781 +0530
@@ -221,7 +221,7 @@

   log_notice "WSREP: Running position recovery with --log_error=$wr_logfile"

- $mysqld_cmd --log_error=$wr_logfile --wsrep-recover
+ eval_log_error "$mysqld_cmd --log_error=$wr_logfile --wsrep-recover"

   local rp="$(grep 'WSREP: Recovered position:' $wr_logfile)"
   if [ -z "$rp" ]; then

I don't think this is a merge regression, this bug has been present ever since wsrep_recover was added to mysqld_safe.

But I presume nobody tried to use malloc-lib with PXC before, so it is failing now.

Another workaround would be to export LD_PRELOAD in the init script.

Was working with Percona-XtraDB-Cluster-server-5.5.29-23.7.1.388

No, it wasn't.

==========================================================
+ chmod 600 /tmp/tmp.VU380MxLV9
+ log_notice WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
+ log_generic daemon.notice WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
+ priority=daemon.notice
+ shift
+ date +%y%m%d %H:%M:%S
+ msg=130418 19:24:35 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
+ echo 130418 19:24:35 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
130418 19:24:35 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
+ echo 130418 19:24:35 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.VU380MxLV9
+ LD_PRELOAD=/usr/lib/libjemalloc.so.1 nohup /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/lib/mysql/Buu.err --open-files-limit=65535 --pid-file=/var/lib/mysql/Buu.pid --log_error=/tmp/tmp.VU380MxLV9 --wsrep-recover
/usr/bin/mysqld_safe: 217: /usr/bin/mysqld_safe: LD_PRELOAD=/usr/lib/libjemalloc.so.1: not found
+ grep WSREP: Recovered position: /tmp/tmp.VU380MxLV9
+ rp=
+ [ -z ]
+ grep WSREP /tmp/tmp.VU380MxLV9
+ grep skipping position recovery
+ skipped=
+ [ -z ]
+ cat /tmp/tmp.VU380MxLV9
+ log_error WSREP: Failed to recover position:
+ log_generic daemon.error WSREP: Failed to recover position:
+ priority=daemon.error

=========================================================================

It failed there silently.

Full log for 5.5.29 here http://sprunge.us/ZRTO

Fix pushed in lp:codership-mysql/5.5-23 r3864

Raghu: it wasn't able to perform wsrep-recover but mysqld was able to run

@Fred,

Yes, that was also a bug. It should fail if it was not able to
wsrep-recover, than fail silently and proceed.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1338