Your Amazon Elastic MapReduce (Amazon EMR) cluster fails to start with the error message "application provisioning failed".

EMR clusters support multiple configuration options that are typically deployed through bootstrap actions that install customer applications to meet design objectives. After customer bootstrap actions are completed, the EMR cluster installs additional applications and ensures that the cluster is properly configured.

If the cluster cannot perform these steps, the cluster fails to start, with the error message “application provisioning failed”. Although there are several potential causes, the most common cause is a problem with the cluster configuration. For example, an EMR cluster fails to start if incorrect credentials are specified for an external Hive metastore.

Review your cluster’s Node Provisioner logs located in the S3 log location at s3::////node//provision-node/ for clues about the cause of the application provisioning failure. Because the logs can be quite verbose, you might want to open an AWS Support case for help interpreting the logs.

EMR, cluster, application provisioning, bootstrap, problem starting


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-05-13