The node count isn't enforced. You can build huge pools if you want. Not sure if this is current, but in the past xapi is/was single threaded. When you move beyond 16 nodes it starts to become painful to manage the system in the event of a pool outage. The master node spends almost 100% of its time sending/receiving updates from the slave and becomes useless to run vms on. Not to mention trying to manage it via XenCenter becomes an exercise in futility.
From: xen-api-boun...@lists.xen.org [mailto:xen-api-boun...@lists.xen.org] On Behalf Of Suman C Sent: Thursday, January 09, 2014 3:02 PM To: xen-api@lists.xen.org Subject: [Xen-API] Number of hosts limit per resource pool Hi, I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to 6.2. One of the configuration limits is 16 hosts per resource pool. I don't have more than 16 hosts to test right away, so I am asking. Is this limit enforced by the code? Or is it a matter of supportability from Citrix? It would be greatly helpful to know among the list of configuration limits, which ones are enforced by the code and why. Can someone address these questions? Thanks Suman
_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
