Yeah, I just finished a test to confirm the above statement on SST.
The status checking will pass just after the SST process terminated/finished. And this process spent ~72min. So the next question need to be answered is why it spend so long to finish SST.
LOG:
root@node-25:~# mysql -uclustercheck -p50cUWiAnI86oXBhx7OcthBer -Nbe "show status like 'wsrep_local_state_comment'"
Warning: Using a password on the command line interface can be insecure.
+---------------------------+--------+
| wsrep_local_state_comment | Synced |
+---------------------------+--------+
Yeah, I just finished a test to confirm the above statement on SST.
The status checking will pass just after the SST process terminated/ finished. And this process spent ~72min. So the next question need to be answered is why it spend so long to finish SST.
LOG: Bhx7OcthBer -Nbe "show status like 'wsrep_ local_state_ comment' " ------- ------- ------- +------ --+ state_comment | Synced | ------- ------- ------- +------ --+
root@node-25:~# mysql -uclustercheck -p50cUWiAnI86oX
Warning: Using a password on the command line interface can be insecure.
+------
| wsrep_local_
+------
mysql 18257 18112 0 07:28 ? 00:00:00 sh -c wsrep_sst_ xtrabackup- v2 --role 'joiner' --address '192.168.0.7' --auth 'root:iM9VWfY1a naR5ZXWconKfZq3 ' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' --defaults- group-suffix '' --parent '18112' ''
the terminate time is Thu Sep 22 08:40:41 UTC 2016