<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">Is RedHat limit node's number, or corosync's code?<br><br><br><br><br><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2017-07-06 11:11:39, "Digimer" <lists@alteeve.ca> wrote:
>On 2017-07-05 09:03 PM, mlb_1 wrote:
>> Hi:
>> I heard corosync-node's number limit to 16£¿ It's true£¿ And Why?
>> Thanks for anyone's answer.
>>
>>
>> https://specs.openstack.org/openstack/fuel-specs/specs/6.0/pacemaker-improvements.html
>>
>>
>> * Corosync 2.0 has a lot of improvements that allow to have up to 100
>> Controllers. Corosync 1.0 scales up to 10-16 node
>
>There is no hard limit on how many nodes can be in a cluster, but Red
>Hat supports up to 16. SUSE supports up to 32, iirc. The problem is that
>it gets harder and harder to keep things stable as the number of nodes
>grow. There is a lot of coordination that has to happen between the
>nodes and it gets ever more complex.
>
>Generally speaking, you don't want large clusters. It is always advised
>to break things up it separate smaller clusters whenever possible.
>
>
>--
>Digimer
>Papers and Projects: https://alteeve.com/w/
>"I am, somehow, less interested in the weight and convolutions of
>Einstein¡¯s brain than in the near certainty that people of equal talent
>have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
</pre></div><br><br><span title="neteasefooter"><p> </p></span>