Lack of sufficient available resources is one of the most common reasons why creating a
cluster may fail. Some of the specific resource issues that commonly occur can
include:
- There are not enough free resources remaining within the current tenant (a violation
of tenant quotas) to create all of the requested virtual nodes for the cluster.
- The deployment does not have enough free resources available, even if the tenant
quota is not violated.
- The host(s) that match any specified placement constraint(s) do not have enough free
resources available, regardless of the total amount of free resources in the
deployment.
- The deployment and/or matching host(s) do not have enough free resources to
start a stopped cluster.
- An attempt to create at least one of the virtual nodes was unable to find enough
free resources provided by any single host. This may occur because a virtual node
must “fit” within a single host; it cannot span across or use resources drawn from
multiple hosts.
- Clusters with HBase or YARN High Availability enabled require the first three
virtual nodes of a cluster to be placed on different hosts for optimal protection.
If the hosts do not have enough free resources to meet this requirement, then
cluster creation will fail. This requirement is not enforced if the deployment has
fewer than three hosts; however, the cluster will be more vulnerable to subsequent
host or node failures.
If a cluster creation attempt fails for lack of resources, you can attempt the following
solutions:
- Use a smaller number of nodes, or a flavor with smaller vCPU/memory requirements, if
that is still acceptable for the application requirements.
- Free up resources by either:
- Stopping or deleting unused or
lower-priority clusters in the tenant.
- Removing one or more
placement constraint(s), if possible.
- If you selected YARN High Availability for the cluster but can make do without, try
creating the cluster again without enabling YARN High Availability.
- Contact the Tenant/Project Administrator about raising the
tenant/project quota (if a quota violation caused the error).
- Contact the Platform Administrator about adding more hosts to the deployment.