Hmm. That is also a possibility. Thanks Chrissie. On Tue, Jun 28, 2016 at 6:13 PM, Christine Caulfield <ccaul...@redhat.com> wrote:
> On 28/06/16 13:27, Nikhil Utane wrote: > > Hi Klaus, > > > > I am using multicast to avoid having to configure the host names. > > > > To be honest, if you're serious about keeping the number of nodes down, > then careful management is the way to do it, looking for a technical fix > is not the answer. Yes, you could reduce the #define in corosync, but > you risk hitting previously unknown bugs that might be caused by that > number being hit for real. > > > Chrissie > > > -Thanks > > Nikhil > > > > On Tue, Jun 28, 2016 at 5:53 PM, Klaus Wenninger <kwenn...@redhat.com > > <mailto:kwenn...@redhat.com>> wrote: > > > > On 06/28/2016 01:18 PM, Nikhil Utane wrote: > > > Hi, > > > > > > I want to limit the number of nodes that can form a cluster to > single > > > digit (say 6). I can do it using application-level logic but would > > > like to know if there is any option in Corosync that would do it > for > > > me. (Didn't find one). > > Going unicast you have full control over who is in your cluster and > who > > is not... > > Not the direct answer to your question but maybe it solves your > problem > > though. > > > If there is some #define, can I change it without any side-effect? > > > > > > -Thanks > > > Nikhil > > > > > > > > > _______________________________________________ > > > Users mailing list: Users@clusterlabs.org > > <mailto:Users@clusterlabs.org> > > > http://clusterlabs.org/mailman/listinfo/users > > > > > > Project Home: http://www.clusterlabs.org > > > Getting started: > > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > > Bugs: http://bugs.clusterlabs.org > > > > > > _______________________________________________ > > Users mailing list: Users@clusterlabs.org <mailto: > Users@clusterlabs.org> > > http://clusterlabs.org/mailman/listinfo/users > > > > Project Home: http://www.clusterlabs.org > > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.org > > > > > > > > > > _______________________________________________ > > Users mailing list: Users@clusterlabs.org > > http://clusterlabs.org/mailman/listinfo/users > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.org > > > > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org >
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org