SST Method from Rsync to xtrabackup

614 views
Skip to first unread message

hunter86bg

unread,
Mar 25, 2016, 9:58:44 AM3/25/16
to codership
Dear Friends,

I have a 3 node cluster (mysql 5.6) on RHEL 7. Up to now , I was using rsync as SST method and now it's time to switch to xtrabackup.
After changing to wsrep_sst_method=xtrabackup

What packages are needed for the SST method to be working without blocking the donor ?

Cole Busby

unread,
Mar 25, 2016, 5:14:00 PM3/25/16
to codership
Hey Hunter,

Percona's toolkit actually mentions that you should use wsrep_sst_method=xtrabackup-v2 and that would be the non-blocking synchronization method. I have performed this change on an Ubuntu client and unfortunately not on a Red Hat System. However I believe the method is similar.

Here is the instructions on installing Percona's Xtrabackup for Redhat via Repo's.

Here is the information regarding which versions of xtrabackup to use and why.

Hope that helps!
-Cole

hunter86bg

unread,
Mar 26, 2016, 3:46:44 PM3/26/16
to codership
Dear Cole,

thanks a lot for providing the links. As the cluster is still in testing , the SST method was way behind in the priority list.
Thanks for reminding to switch to "xtrabackup-v2" method.I'll have to contact our team to update to the latest percona-xtrabackup version ,as it seem's we are a little bit behind in versions. I'll provide feedback once I have tested successfully xtrabackup-v2 SST.
By the way, do you know what method is used for IST,as it's non-blocking but I haven't installed percona-xtrabackup ?I guess it's using the replication channel...

Cole Busby

unread,
Mar 28, 2016, 1:22:13 PM3/28/16
to codership
Hunter,

The IST is non-blocking for the donor only. More information found here. I unfortunately could not find more specific information as to how it is used.

hunter86bg

unread,
Mar 30, 2016, 12:35:50 PM3/30/16
to codership
Ok,
here is what happened.
I've added
wsrep_sst_method=xtrabackup-v2
wsrep_sst_auth=user:pass
[xtrabackup]
tmpdir=path_to_temp_dir

and installed "socat" package . Check your my.cnf permissions (my version of xtrabackup was searching for /etc/my.cnf).
At last , just start mysql.
If you use "systemctl start mysql" it will timeout , but eventually when the SST transfer is completed - it will start the mysql server without any issues. To see the status in systemd , just run the starting command and it will show it's running.

With the non-blocking xtrabackup-v2 method , everything is working as expected.

Rameez

unread,
Apr 15, 2016, 4:13:46 AM4/15/16
to codership
Finally I found the issue. 

*  In node2 I added a parameter decompress to extract the data compressed by qpress with the extension .qp.
*  Upgraded from bugged version of xtrabackup 2.2 to 2.4 (resolved memory issues)
*  Upgraded mariadb and galera version.

qpress helps to compress the data to 28% of the actual size of the data dir/whole DB.

node1
[sst]
streamfmt=xbstream
transferfmt=socat
compressor="pigz"
decompressor="pigz -d"

[xtrabackup]
compress
#compact
parallel=8
compress-threads=8
rebuild-threads=8

node2
[sst]
streamfmt=xbstream
transferfmt=socat
inno-apply-opts="--use-memory=5G"
compressor="pigz"
decompressor="pigz -d"

[xtrabackup]
decompress
#compact
parallel=8
compress-threads=8
rebuild-threads=8

I appreciate the members(Cole and Hunter) who gave quick response and useful suggestion to my questions.

Thank you very much guys.


On Friday, 25 March 2016 21:58:44 UTC+8, hunter86bg wrote:
Dear Friends,

I have a 3 node cluster (mysql 5.6) on RHEL 7. Up to now , I was using rsync as SST method and now it's time to switch to xtrabackup.
After changing to wsrep_sst_method=xtrabackup 

What packages are needed for the SST method to be working without blocking the donor ?
Reply all
Reply to author
Forward
0 new messages