Known Issues and Workarounds in Cloudera Director 1

When using a Cloudera Manager package repository or CDH/parcel repository URL that only specifies the major or minor versions, Cloudera Director may incorrectly use the latest available version when trying to grow a cluster.

Workaround: Use a parcel repository that is specified down to the maintenance version. This will ensure that Cloudera Director finds the correct version during cluster growth.

For Cloudera Manager: http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.3.3/

For CDH: http://archive.cloudera.com/cdh5/parcels/5.3.3/

If the shell environment variables AWS_ACCESS_KEY and AWS_SECRET_KEY are set in the shell within which the Cloudera Director server component runs, then the server may use those credentials in communications with AWS when a Cloudera Director environment does not have them configured properly. When those credentials differ from the intended ones, EC2 instances may be allocated under unexpected accounts. Cloudera recommends ensuring that the environment variables are not set.

Severity: Medium

Workaround: Ensure that the Cloudera Director environment, defined in a client configuration file or in a server, has values for the keys that are present and correct.

Director is unable to resize root partition on Centos 6.5 HVM AMIs. This is due to a bug in the AMI. For more information, see the CentOS Bug Tracker.

Workaround: None.

Although you can deploy Flume through Cloudera Director, you must start it manually using Cloudera Manager after Cloudera Director bootstraps the cluster.

Workaround: Start Flume manually using Cloudera Manager after Cloudera Director bootstraps the cluster.

Cloudera Director cannot setup external databases for Oozie, Hue, and Sqoop2, the way it does with Hive.

Workaround: Set up the databases for these services as described in Cloudera Manager and Managed Service Databases. Provide the database properties such as host address and username to Cloudera Director in the relevant Oozie service configuration section.

Impala daemons attempt to connect over IPv6.

Workaround: Add the following command part of the instance bootstrap script: sysctl -w net.ipv6.conf.all.disable_ipv6=1.

DNS queries occasionally timeout with AWS VPN.

Workaround: Cloudera recommends that you install NSCD (name service cache daemon) on all cluster nodes via a bootstrap script. By default Linux does not cache DNS lookups. For more information, see the Linux NSCD man page.

If you are including 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 due to a MySQL bug that is exposed through using MySQL 5.6.5 or later with the MySQL JDBC driver (used by Cloudera Director) version 5.1.19 or earlier. For information on the MySQL bug, see the MySQL bug description.

Workaround: Select an older MySQL version that avoids this bug, depending on the driver version installed by Cloudera Director from your platform's software repositories.

Terminating a cluster that is 'Bootstrapping' stops on-going processes, but keeps the cluster in 'Bootstrapping' phase.

Severity: Low

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