We can see the mysql service is not restarted during the re-deployment (see the process' start-up time). So there is no more fresh, which means there is no SST in the 2nd re-deployment.
root@node-25:~# date
Thu Sep 22 09:30:48 UTC 2016
root@node-25:~# ps -ef | grep mysqld_safe
root 11742 7377 0 09:30 pts/3 00:00:00 grep --color=auto mysqld_safe
root 17159 1 0 07:28 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe --pid-file=/var/run/resource-agents/mysql-wss/mysql-wss.pid --socket=/var/run/mysqld/mysqld.sock --datadir=/var/lib/mysql --user=mysql
We can see the mysql service is not restarted during the re-deployment (see the process' start-up time). So there is no more fresh, which means there is no SST in the 2nd re-deployment. mysqld_ safe --pid-file= /var/run/ resource- agents/ mysql-wss/ mysql-wss. pid --socket= /var/run/ mysqld/ mysqld. sock --datadir= /var/lib/ mysql --user=mysql
root@node-25:~# date
Thu Sep 22 09:30:48 UTC 2016
root@node-25:~# ps -ef | grep mysqld_safe
root 11742 7377 0 09:30 pts/3 00:00:00 grep --color=auto mysqld_safe
root 17159 1 0 07:28 ? 00:00:00 /bin/sh /usr/bin/