Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).



A cluster terminates with a INTERNAL_ERROR_SPOT_NO_CAPACITY_PRIMARY error when there isn't enough capacity to fulfill a Spot Instance request for your primary node. For more information, see Spot Instances in the Amazon EC2 User Guide for Linux Instances.


To resolve this error, specify instance types for your cluster that are within your price target, or increase your price limit for the same instance type.

To troubleshoot the failed EMR cluster, refer to the ErrorDetail information returned from the DescribeCluster and ListClusters APIs. For more information, see Error codes with ErrorDetail information. The ErrorData array within ErrorDetail returns the following information for this error code:


The ID for the primary instance of the cluster that failed.


The instance type that is out of capacity.


The Availability Zone that your subnet resolves to.


The public URL of the documentation for the error code.

Steps to complete

Perform the following steps to troubleshoot your cluster configuration strategy, and then launch a new cluster:

  1. Review the best practices for Amazon EC2 Spot Instances and review your cluster configuration strategy. For more information, see Best practices for EC2 Spot in the Amazon EC2 User Guide for Linux Instances and Best practices for cluster configuration.

  2. Modify your instance type configurations and create a new cluster with your updated request.

  3. If the issue persists, use On-Demand capacity for your primary instance.