Code review comment for lp:~hrvojem/percona-xtradb-cluster/pxc-12

"The downside of `mysqldump` and `rsync` is that the cluster becomes *READ-ONLY* while data is being copied from one node to another (SST applies :command:`FLUSH TABLES WITH READ LOCK` command). "

The cluster becomes read-only, or the Donor node? I think only the Donor node (but I could be wrong, I haven't done much with mysqldump and rsync.

"+ $ yum install Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client xtrabackup"

xtrabackup is a dependency of PXC server, AFAIK.

"+ wsrep_cluster_address=gcomm://192.168.70.72,192.168.70.73"

Actually, there's no reason why node1's ip can't be in the list, Galera is smart enough to remove it -- and this gives you a setting that you can make identical on all the nodes.

Do we need innodb_locks_unsafe_for_binlog?

I wouldn't necessarily recommend using root for SST, but a separate user. Include a link to the xtrabackup doc about grants necessary.

Why are you not setting wsrep_cluster_name?

"40 +.. note::
441 +
442 + Starting the cluster using the ``/etc/init.d/myslq start --wsrep-cluster-address="gcomm://"`` will only work on RedHat based distributions (like CentOS). This method won't work on Debian/Ubuntu due to difference in the init script.
443 +"

Spelling of 'mysql' ^^
How would you bootstrap if you can't use the init script?

"+This method uses :program:`rsync` to copy files from donor to the joining node. In some cases this can be faster than using the |XtraBackup| but requires the global data lock which will block writes to the cluster. This method doesn't require username/password credentials to be set up in the variable :variable:`wsrep_sst_auth`."

- Again, I think you mean 'node' here, not 'cluster'.