On 04.01.2017 13:52, Jan Friesse wrote:
Variables you can try tweak.
- Definitively start with increase totem.config (default 1000, you can
try 1)
what does that do? Haven't found it in corosync.conf(5)
- If it doesn't help, try increase totem.join (default is 50, 1000 may
work) and
Hi Honza,
On 04.01.2017 13:52, Jan Friesse wrote:
At least those limits doesn't seem to get enforced, as a 64 node cluster
seems to work, although a bit shaky.
No, they are not enforced. 16/32 are official supported number of nodes.
Basically, this is number what was tested and known to
On 04.01.2017 11:25, Kristoffer Grönlund wrote:
Arne Jansen <li...@die-jansens.de> writes:
Hi,
I've built corosync for solaris and am trying to build a largish
cluster. I started corosync with default configuration on an
increasing number of nodes, one by one. At around 70 nodes the
c
Hi,
I've built corosync for solaris and am trying to build a largish
cluster. I started corosync with default configuration on an
increasing number of nodes, one by one. At around 70 nodes the
cluster breaks down. Below is an excerpt from the logfile on the
first node.
When the cluster breaks
