[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Number of hosts limit per resource pool

  • To: Suman C <schakrava@xxxxxxxxx>, "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>
  • From: Joseph Hom <jhom@xxxxxxxxxxxxx>
  • Date: Thu, 16 Jan 2014 20:32:45 +0000
  • Accept-language: en-US
  • Delivery-date: Thu, 16 Jan 2014 20:32:58 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: AQHPDYBX/U008gozFEWaGW/uvoNeo5qH2IgA
  • Thread-topic: [Xen-API] Number of hosts limit per resource pool

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-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On Behalf Of Suman C
Sent: Thursday, January 09, 2014 3:02 PM
To: xen-api@xxxxxxxxxxxxx
Subject: [Xen-API] Number of hosts limit per resource pool



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?



Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.