# Incremental option for wsrep\_sst\_method

**URL:** <https://forums.percona.com/t/incremental-option-for-wsrep-sst-method/2456>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [August 2, 2012, 10:44am UTC](https://forums.percona.com/t/incremental-option-for-wsrep-sst-method/2456 "2012-08-02T10:44:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mandm](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mandm](https://forums.percona.com/u/mandm)\
**Post date:** [August 2, 2012, 10:44am UTC](https://forums.percona.com/t/incremental-option-for-wsrep-sst-method/2456/1 "2012-08-02T10:44:55Z")

</div>

Hi  
Currently i am using this configuration for setting up a cluster on node1

node 1  
binlog\_format=ROW  
wsrep\_provider=/usr/lib64/libgalera\_smm.so  
wsrep\_cluster\_address=gcomm://  
wsrep\_slave\_threads=2  
wsrep\_cluster\_name=dev\_cluster  
wsrep\_sst\_method=rsync  
wsrep\_node\_name=node1  
innodb\_locks\_unsafe\_for\_binlog=1  
innodb\_autoinc\_lock\_mode=2  
wsrep\_replicate\_myisam=1

node2  
wsrep\_provider=/usr/lib64/libgalera\_smm.so  
wsrep\_cluster\_address=gcomm://10.1.0.1:4567  
wsrep\_slave\_threads=2  
wsrep\_sst\_method=rsync  
wsrep\_cluster\_name=dev\_cluster  
binlog\_format=ROW  
default\_storage\_engine=InnoDB  
innodb\_autoinc\_lock\_mode=2  
innodb\_locks\_unsafe\_for\_binlog=1  
wsrep\_replicate\_myisam=1

and what i understand is in case node 2 goes down and comes backup, it will perform a full rsync from node1 /var/lib/mysql directory in order to get unto date with the data and depemding on the size of data it can take much longer for big db’s  
so here are my questions

1. how do i configure this to only patch all the incremental updates from node1?
2. how does node 1 know where to store all the increments for node2 to patchup once it is up?
3. How does this scenario work when node2 is up and node1 goes down and comes back up?

Thanks once again…  
i am using  
Server version: 5.5.24-55-log Percona XtraDB Cluster (GPL), wsrep\_23.6.r341  
on ubuntu 10.04

---

<div class="post-metadata">

**Author:** ![lefred](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lefred/32/16885_2.png) [@lefred](https://forums.percona.com/u/lefred)\
**Post date:** [August 14, 2012, 2:26am UTC](https://forums.percona.com/t/incremental-option-for-wsrep-sst-method/2456/2 "2012-08-14T02:26:43Z")

</div>

Hi,

2 nodes is not the recommended amount of members for an optimal cluster.

Also, if you don’t what that SST blocks the donor, use xtrabackup

All your other questions are detailed in [http://www.mysqlperformanceblog.com/2012/07/25/percona-xtrad](http://www.mysqlperformanceblog.com/2012/07/25/percona-xtrad) b-cluster-failure-scenarios-with-only-2-nodes/

regards,

---

<div class="post-metadata">

**Author:** ![stephon](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/stephon/32/895_2.png) [@stephon](https://forums.percona.com/u/stephon)\
**Post date:** [October 8, 2012, 2:13am UTC](https://forums.percona.com/t/incremental-option-for-wsrep-sst-method/2456/3 "2012-10-08T02:13:03Z")

</div>

lefred wrote on Tue, 14 August 2012 00:56

> [@](#):
>
> Hi,
> 
> 2 nodes is not the recommended amount of members for an optimal cluster.
> 
> Also, if you don’t what that SST blocks the donor, use xtrabackup
> 
> All your other questions are detailed in [http://www.mysqlperformanceblog.com/2012/07/25/percona-xtrad b-cluster-failure-scenarios-with-only-2-nodes/](https://http)
> 
> regards,

Hello

I found that using xtrabackup results the same situation.  
the cluster sync rate also in 3~4KB/s

or is there a better way to switch MySQL multi-master scenario to Percona cluster?

Thanks a lot