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

Cloudera Manager 4 and CDH 4 have reached End of Maintenance (EOM) on August 9, 2015. Cloudera will not support or provide patches for any of the Cloudera Manager 4 or CDH 4 releases after that date.

Adding Role Instances

After creating a service using one of the wizards, you can add a role instance to that service. For example, after initial installation in which you added the HDFS service, you can add a DataNode to a host where one was not previously running.

In a CDH4 cluster, some services provide roles that are not available with CDH3. For example, HDFS in CDH4 supports HttpFS, so that role is available as part of the HDFS service.

CDH4 HDFS also now provides a Failover Controller role, which is added to the HDFS service as a companion to each NameNode when you enable Automatic Failover after enabling High Availability. It is recommended that you let Cloudera Manager add this role as appropriate, rather than adding it manually.

There is also a new role called Gateway available in both CDH3 and CDH4 clusters for the HDFS, MapReduce, and HBase services (and for YARN in CDH4) . You can add a Gateway role to a host that does not otherwise have a CDH service installed — this enables Cloudera Manager to install and manage client configurations on that host. This is a convenient way to manage configurations on your CDH clients. There is no process associated with a Gateway role, and its status will always be Stopped.

To add a role instance:

  1. From the Services tab, select the service for which you want to add a role instance. For example, click the HDFS service link if you want to add a DataNode role instance for that HDFS service.
  2. Click the Instances tab.
  3. Click the Add button.
  4. Follow the instructions in the wizard to add the role instance. During the wizard, Cloudera Manager will list the existing roles on hosts, recommend configuration settings such as data directory paths and heap sizes depending on the roles. If the new roles are assigned to the same host as roles of another service, Cloudera Manager may recommend configuration changes such that heap allocations of all the roles on the host can be accommodated. You can change some settings, such as data directory paths, before continuing. If you click Continue after making changes, the new roles will be created with your configuration settings and configuration changes will be made. If you click Skip, the new roles will be created with the Cloudera Manager recommended changes. If necessary, you can reconfigure the new roles later by navigating to the Configurations tab for each role or of the service that these roles belong to.
  5. The wizard finishes by performing any actions necessary to prepare the cluster for the new role instances. For example, new DataNodes are added to the NameNode's dfs_hosts_allow.txt file.
  6. The new role instance is configured with the Default role group for its role type, even if there are multiple role groups for the role type. If you want to use a different role group, you can go to the Role Groups page under the Configuration tab for the service, and move the role instance to a different role group. See Managing Role Groups for more information.
  7. The new role instances are not started automatically. You can start them on the service's Instances page.
This page last updated September 8, 2015