Init script should manage startup case where SST is needed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
When starting a PXDC node which needs an SST due to crash or other reasons, the SysV Init script provided with Percona's Debian package simply shows the startup as failed like below but this behavior is false :
# /etc/init.d/mysql start
[FAIL] Starting MySQL (Percona XtraDB Cluster) database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
By looking at the mysql error logs, we can see that mysqld is started and doing recover from another node in the cluster.
I think a better approach would be at least to informed that an SST is in progress rather than failing like this is actually the case because there is no information for the user that an SST is occuring in the background and so the user can thinks that mysql did not succeed to start and tries to stop/restart it.
Regards,
Laurent
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #1 |
Yes, that is right.
I propose checking for mysqld process and socket being
inaccessible (with mysqladmin ping) as indicator of this (which
should be fine since otherwise mysqld process should end soon). This
should also help in other instances like blocking LRU restore.