wsrep_sst_donor question/suggestion

657 views
Skip to first unread message

Graham Green

unread,
Jun 20, 2013, 9:03:16 PM6/20/13
to codersh...@googlegroups.com
In my testing I have found that if I have the wsrep_sst_donor variable is set in my.cnf file on node1 to wsrep_sst_donor=node4 for example. I noticed that if node4 is down when node1 is started, node1 will fail to start.

Is there a reason for node1 not to just trying a random node in the cluster (as it would if wsrep_sst_donor was not set)?
If not, I think this would be a worthwhile addition to the process, either that or perhaps a comma separated list of nodes to try ie
wsrep_sst_donor=node4,node3
So in the event of the preferred node (node4) not being available, node3 would be used.

Thanks
Graham

Alex Yurchenko

unread,
Jun 21, 2013, 9:55:31 AM6/21/13
to codersh...@googlegroups.com
On 2013-06-21 04:03, Graham Green wrote:
> In my testing I have found that if I have the wsrep_sst_donor variable
> is
> set in my.cnf file on node1 to wsrep_sst_donor=node4 for example. I
> noticed
> that if node4 is down when node1 is started, node1 will fail to start.
>
> Is there a reason for node1 not to just trying a random node in the
> cluster
> (as it would if wsrep_sst_donor was not set)?

The thing here is: what if you want to use precisely that node and
don't want it to try random one. I'd suppose that is often the reason
why people set wsrep_sst_donor - that they want control. Trying a random
one arguably makes this control weaker.

> If not, I think this would be a worthwhile addition to the process,
> either
> that or perhaps a comma separated list of nodes to try ie
> wsrep_sst_donor=node4,node3

https://bugs.launchpad.net/galera/+bug/1129512

> So in the event of the preferred node (node4) not being available,
> node3
> would be used.
>
> Thanks
> Graham

--
Alexey Yurchenko,
Codership Oy, www.codership.com
Skype: alexey.yurchenko, Phone: +358-400-516-011

Graham Green

unread,
Jun 21, 2013, 12:23:46 PM6/21/13
to codersh...@googlegroups.com
Thanks Alexey
Good to know the option to specify more than one node is in the pipeline.
Reply all
Reply to author
Forward
0 new messages