Known Issues and Workarounds in Cloudera Director

If the cloud instance hosting Cloudera Manager for a deployment is deleted without going through Cloudera Director, then deployment termination may fail while attempting to clean up the Kerberos credentials associated with Cloudera Manager. This failure only occurs when Cloudera Director cannot contact Cloudera Manager directly over its web port and must instead use an SSH tunnel to reach it.

Workaround: Command Cloudera Director to terminate the deployment again, and it will succeed.

Cloudera bug: DIR-8331

Azure simple setup cluster installation fails when the cluster name contains capital letters.

Workaround: Use only lowercase letters in cluster names.

Cloudera bug: DIR-8335

When attempting to launch a cluster with the simple setup procedure, Cloudera Director server may return an HTTP error code of 406 with the message: Could not find acceptable representation. This occurs when there is an error in the data supplied for the cluster, and the server is unable to formulate a correct error response. This error code and message should not occur when the data for simple cluster setup is correct.

Workaround: Look in the Cloudera Director server log to find the underlying problem with the data supplied for the cluster.

Cloudera bug: DIR-8241

With clusters on Microsoft Azure that have auto-repair enabled in Cloudera Director 2.6 and higher, healthy instances can sometimes be removed when there is a connection failure between Cloudera Director and Azure.

Workaround: Do not enable auto-repair on Azure for Cloudera Director 2.6 and higher.

Cloudera bug: DIR-8291

Newly added instance groups are not automatically configured. Roles on the new instances will be given the same configuration as existing roles even if the new instance uses a different instance type than the old instances.

Workaround: Update the role group in Cloudera Manager after the cluster update completes.

Cloudera Bug: DIR-5102

Cloudera Director evicts terminated deployment, cluster, and external database server entities from its database before removing the environment. Cloudera Director also performs the same eviction on a periodic basis. A 500 response may be returned if the two evictions occur concurrently.

Workaround: Retry environment deletion.

Parsing of a Cloudera Director configuration file can produce errors indicating that the environment name and, sometimes additionally, the deployment name are too long, even though the names were not specified in the file. This is a consequence of Cloudera Director automatically generating those names, based on the cluster name, when they are not explicitly given in the file. When the cluster name is long, the automatically-generated names exceed the length limits.

environmentName: MyEnvironment
deploymentName: MyDeployment

Cloudera Bug: DIR-6301

Standing up a cluster with a large number of EBS volumes might trigger rate limiting on EBS allocation requests. The effect can spread to other calls from Cloudera Director to AWS.

Workaround: No more than 10 EBS volumes should be attached at a time.

Cloudera Bug: DIR-4283

Cloudera Navigator Key Trustee Server cannot be one of the services deployed by Cloudera Director.

Workaround: Set up Cloudera Navigator Key Trustee Server via Cloudera Manager if using Cloudera Director 2.4 and above.

Cloudera Bug: DIR-1757

Cloudera Director cannot set up external databases for Sqoop2.

Workaround: Set up databases for this service as described in Cloudera Manager and Managed Service Databases.

Cloudera Bug: DIR-1832

Clusters deployed in Cloudera Manager version 5.4 and lower might not have metrics displayed in the web UI if these clusters share the same name as previously deleted clusters.

Workaround: Use Cloudera Manager 5.5 and higher.

Cloudera Bug: DIR-2422

If the Cloudera Manager username and password are changed directly in Cloudera Manager, Cloudera Director can no longer add new instances or authenticate with Cloudera Manager. Username and password changes must be implemented in Cloudera Director as well. For more information on keeping Cloudera Director and Cloudera Manager in sync, see CDH Cluster Management Tasks.

Workaround: Use the Cloudera Director web UI to update the Cloudera Manager username and password.

Cloudera Bug: DIR-690

Cloudera Director Server uses the AWS credentials from a configured Environment, as defined in a client configuration file or through the Cloudera Director web UI. If the Environment is not configured with credentials in Cloudera Director, the Cloudera Director server instead uses the AWS credentials that are configured on the instance on which the Cloudera Director server is running. When those credentials differ from the intended ones, EC2 instances might be allocated under unexpected accounts. Ensure that the Cloudera Director server instance is not configured with AWS credentials.

Severity: Medium

Workaround: Ensure that the Cloudera Director Environment has correct values for the keys. Alternatively, use IAM profiles for the Cloudera Director server instance.

Cloudera Bug: DIR-1040

Cloudera Director cannot resize the root partition on Centos 6.5 HVM AMIs. This is caused by a bug in the AMIs. For more information, see the CentOS Bug Tracker.

Cloudera Bug: DIR-757

If you include Hive in your clusters and configure the Hive metastore to be installed on MySQL, Cloudera Manager might report, "The Hive Metastore canary failed to create a database." This is caused by a MySQL bug in MySQL 5.6.5 or higher that is exposed when used with the MySQL JDBC driver (used by Cloudera Director) version 5.1.19 or lower. For information on the MySQL bug, see the MySQL bug description.

Workaround: Depending on the driver version installed by Cloudera Director from your platform's software repositories, select an older MySQL version that does not have this bug.

Cloudera Bug: DIR-923