I can confirm that innodb_blocking_buffer_pool_restore=ON solves the issue but with a weird side-effect. Galera tries to restore the wsrep_position and with that option enabled it spends a lot of time on that part:
130205 13:10:38 mysqld_safe Starting mysqld daemon with databases from /data/mysql
130205 13:10:38 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.nci5tZ9xZF
130205 13:16:37 mysqld_safe WSREP: Recovered position 402367df-5fd0-11e2-0800-58b321ec9eec:518510084
Almost 6 minutes spent above when without the innodb_blocking_buffer_pool_restore=ON it is pretty much instant.
It is not that it restores the buffer pool pages at that point as the log indicates later on:
130205 13:16:45 InnoDB: Restoring buffer pool pages from ib_lru_dump
130205 13:22:52 InnoDB: Completed reading buffer pool pages (requested: 3178478, read: 3178076)
I can confirm that innodb_ blocking_ buffer_ pool_restore= ON solves the issue but with a weird side-effect. Galera tries to restore the wsrep_position and with that option enabled it spends a lot of time on that part:
130205 13:10:38 mysqld_safe Starting mysqld daemon with databases from /data/mysql /tmp/tmp. nci5tZ9xZF 5fd0-11e2- 0800-58b321ec9e ec:518510084
130205 13:10:38 mysqld_safe WSREP: Running position recovery with --log_error=
130205 13:16:37 mysqld_safe WSREP: Recovered position 402367df-
Almost 6 minutes spent above when without the innodb_ blocking_ buffer_ pool_restore= ON it is pretty much instant.
It is not that it restores the buffer pool pages at that point as the log indicates later on:
130205 13:16:45 InnoDB: Restoring buffer pool pages from ib_lru_dump
130205 13:22:52 InnoDB: Completed reading buffer pool pages (requested: 3178478, read: 3178076)
What do you think ?