This is the documentation for Cloudera Manager 4.8.2.
Documentation for other versions is available at Cloudera Documentation.

Cloudera Manager Frequently Asked Questions

This guide answers frequently asked questions about Cloudera Manager.

General Questions

What are the new features of Cloudera Manager 4.7?

For a list of new features in Cloudera Manager 4.7, see New Features in Cloudera Manager 4.

What operating systems are supported?

See Cloudera Manager Requirements for more detailed information on which platforms are supported.

What database platforms are supported?

See Cloudera Manager Requirements for more detailed information on which database systems are supported.

What are the differences between the Standard and the Enterprise Versions of Cloudera Manager?

Cloudera Standard includes a free version of the commercially-available Cloudera Manager product. Both the Standard and Enterprise versions automate the installation, configuration, and monitoring of CDH3 or CDH4 on an entire cluster. Cloudera Enterprise provides additional functionality.

The full-featured version of Cloudera Manager is available as part of the Cloudera Enterprise subscription offering, and requires a license.

See the matrix at What are the Differences Between the Cloudera Standard and Enterprise Versions? for a comparison of the two versions. You can also view a discussion of the differences at http://www.cloudera.com/content/cloudera/en/products/cloudera-manager.html.

If you are not an existing Cloudera customer, contact Cloudera Sales using this form or call 866-843-7207 to obtain the full-featured version of Cloudera Manager.

If you are already a Cloudera customer and you need to upgrade the from Cloudera Standard to Cloudera Enterprise, contact Cloudera Support to obtain a license.

What version of CDH is required for Cloudera Manager 4.7?

See Cloudera Manager Requirements for detailed information.

Can I upgrade CDH using Cloudera Manager?

Yes, as of Cloudera Manager 4.5 you can upgrade to CDH4.1.2 or later from within the Cloudera Manager Admin Console using parcels. Furthermore, once you have installed or upgraded CDH using parcels, you can perform rolling upgrades on your CDH services. If you have HDFS High Availability configured and enabled, you can perform a rolling upgrade on your cluster without taking the entire cluster down.

  Important: Cloudera Manager version 3.x and CDH3 have reached End of Maintenance (EOM) as of June 20, 2013. Cloudera will not support or provide patches for any of the Cloudera Manager version 3.x and CDH3 releases. Even though Cloudera Manager 4.x will continue to support CDH3, it is strongly recommended that you upgrade to CDH4. See Upgrading existing installations of CDH3 to CDH4 for more details.

For instructions on upgrading CDH4 to a newer version, see Upgrading CDH4 in a Cloudera Manager Deployment. For instructions on upgrading from CDH3 to CDH4, see Upgrading CDH3 to CDH4 in a Cloudera Manager Deployment.

What version of CDH does Cloudera Manager 4.7 install?

Cloudera Manager 4.7 allows you to install any version of CDH3 or CDH4.

Where are CDH libraries located when I distribute CDH using parcels?

With parcel software distribution, the path to the CDH libraries is /opt/cloudera/parcels/CDH/lib instead of the usual /usr/lib.

What upgrade paths are available for Cloudera Manager, and what's involved?

For instructions about upgrading, see Upgrading Cloudera Manager.

How do I install Cloudera Manager 4.7 in a walled-off environment (no Internet access)?

You can set up a local repository and use it in the installer. For instructions, see Appendix A - Understanding Custom Installation Solutions.

Do slave nodes need access to the Cloudera public repositories for an install with Cloudera Manager?

As of Cloudera Manager 4.5, you can perform an installation or upgrade using the new parcel format. When using parcels, only the Cloudera Manager server requires access to the Cloudera public repositories. Distribution of the parcels to slave nodes is done between the Cloudera Manager server and the slave nodes. See Using Parcels for more information. If you want to install using the traditional packages, nodes only require access to the installation files.

For both parcels and packages, it is also possible to create local repositories that serve these files to the nodes that are being upgraded. If you have established local repositories, no access to the Cloudera public repository is required. For more information, see Creating and Using your own Repository.

Can I use the Service Monitoring features of Cloudera Manager without using Service and Configuration Management?

No. To understand the desired state of the system, we need the global configuration that the service management feature of Cloudera Manager gathers and provides. The Cloudera Manager agent doubles as both the agent for supervision and for monitoring.

Can I run the Cloudera Management services and the Hadoop services on the host where the Cloudera Manager Server is running?

Yes. This is especially common in deployments that have a small number of hosts.

Which sudo commands does Cloudera Manager run?

The sudo commands are:

  • yum (Red Hat/CentOS/Oracle)
  • zypper (SLES)
  • apt-get (Debian/Ubuntu)
  • apt-key (Debian/Ubuntu)
  • sed
  • service
  • /sbin/chkconfig (Red Hat/CentOS/Oracle)
  • /usr/sbin/update-rc.d (Debian/Ubuntu)
  • id
  • rm
  • mv
  • chown
  • install

Does Cloudera Manager Support an API?

Yes. A comprehensive set of APIs for the various features is supported in this version of Cloudera Manager. For more information about the Cloudera Manager API, see Cloudera Manager API. You can download this Cloudera Manager API example that shows how to integrate with Nagios or other systems.

Using Cloudera Manager

How do I set the rack topology script?

Cloudera Manager includes internal rack awareness scripts, but you must specify the racks where the hosts in your cluster are located. If your cluster contains more than 10 hosts, Cloudera recommends that you specify the rack for each host. HDFS and MapReduce will automatically use the racks you specify. For instructions, see Specifying the Racks for Hosts .

How do I configure my daemons to use a custom GC parameter?

Every Java-based role in Cloudera Manager has a configuration setting called "Additional Java configuration options for <role>" where you can enter command line options. Commonly, garbage collection flags or extra debugging flags would be passed here.

To find the appropriate configuration setting, select the service you want to modify in the Cloudera Manager UI, then use the keyword search to search for the Additional Java configuration options.

You can add configuration options for all instances of a given role by making this configuration change at the Service level. For example, to modify the setting for all DataNodes, select the HDFS service, then modify the "Additional Java configuration options for DataNode" setting).

To modify a configuration option for a given instance of a role, select the service, then select the particular role instance (e.g. a specific DataNode) you want to modify. The configuration settings you modify will apply to the selected role instance only.

For detailed instructions see the Modifying Configuration Settings section of Managing Clusters with Cloudera Manager.