PXC innodb_buffer_pool_restore_at_startup and wsrep_recovery
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Raghavendra D Prabhu | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We have noticed an issue on PXC when we have 30GB of buffer pool and the option innodb_
When the node joins (state JOINER ) the cluster before the buffer pool restore is done reading all the pages it had loaded last time cluster flow control will be paused and the whole cluster will stall as the newly joined node is not able to keep up due to lack of io which is being consumed by the buffer pool restore operation. In our case with our workload it may stay stalled for 4-5 mins.
It may not be a bug but it would be best if it was possible to have the buffer pool restore operation complete first and then the wsrep continue joining the cluster or the other way around. Now percona server's innodb_
Related branches
Changed in percona-xtradb-cluster: | |
status: | Triaged → Fix Released |
status: | Fix Released → Fix Committed |
Changed in percona-xtradb-cluster: | |
status: | Fix Committed → Fix Released |
you can use innodb_ blocking_ buffer_ pool_restore= ON
to make sure that restore operation is complete.