Known Issues and Workarounds in Cloudera Director

In Cloudera Director 2.2, if you attempt to terminate a cluster or deployment in the BOOTSTRAP_FAILED stage, it may go back into the BOOTSTRAPPING stage and return the following exception message: java.util.concurrent.TimeoutException: Pipeline did not complete in 10 SECONDS. In this situation, terminating the deployment or cluster a second time should terminate the cluster or deployment as expected. This can also happen in Cloudera Director 2.1, but the exception message will be the following more generic message: 500 internal server error.

Workaround: Terminate the cluster again.

When you bootstrap or validate a cluster that has the HUE_LOAD_BALANCER role, Cloudera Director generates an unknown role type warning for the role.

Workaround: You can ignore the warning.

Cluster bootstrap fails when using Cloudera Manager 5.9.0 with both Kafka 2.0 and Sentry.

Workaround: If Kafka and Sentry are required on the same cluster, use Cloudera Manager 5.8 or below.

Cloudera Director sometimes fails to detect stale services properly when restarting a cluster.

Workaround: If the cluster includes stale services after a restart, restart the cluster again manually through Cloudera Manager.

External databases are not configured for Hue and Oozie in clusters created through the Cloudera Director web UI.

Workaround: External databases can be specified for Hue and Oozie when creating a cluster using the CLI or API.

Cloudera Director automatically installs JDBC drivers on an instance for Cloudera Manager and the CDH clusters it provisions. However, when you use an existing MySQL database with Cloudera Manager, Cloudera Director does not install the JDBC driver, which can result in database connection failures.

Workaround: Select an instance image that already has the JDBC driver installed or use the instance bootstrap script to install the latest available JDBC driver for MySQL.

To install the MySQL JDBC driver, download the driver packages for your platform:

mysql-connector-java
mysql-devel

libmysql-java
libmysqlclient-dev

After you download the JDBC driver packages, you can use a package manager to install the packages.

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

Workaround: Contact Cloudera Support if you need to add Cloudera Navigator Key Trustee Server.

Cloudera Director's web UI does not allow creation of clusters with instance groups that should not have CDH roles deployed on them.

Workaround: Use the CLI or API to create clusters with instance groups that should not have CDH roles deployed on them. At least one instance group in the cluster must specify roles. Otherwise roles will be automatically allocated across all instances.

Cloudera Director's web UI does not allow modification of clusters with instance groups that should not have CDH roles deployed on them, even if they were created using the API.

Workaround: Use the API to modify clusters with instance groups that should not have CDH roles deployed on them.

Cloudera Director is unable to resize XFS partitions, which makes creating an instance that uses the XFS filesystem fail during bootstrap.

Workaround: Use an image with an ext filesystem such as ext2, ext3, or ext4.

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.

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.

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.

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

Modifying a cluster in Cloudera Manager after it is bootstrapped does not cause the cluster state to be synchronized with Cloudera Director. Services that have been added or removed in Cloudera Manager do not show up in Cloudera Director when growing the cluster.

Workaround: None.

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 may 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 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.

Workaround: None.

Terminating a cluster that is bootstrapping stops ongoing processes but keeps the cluster in the bootstrapping phase.

Severity: Low

Workaround: To transition the cluster to the Terminated phase, terminate the cluster again.

If you include Hive in your clusters and configure the Hive metastore to be installed on MySQL, Cloudera Manager may 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.