Cloudera Management Service

Displaying the Cloudera Management Service Status

1. Do one of the following:
   • Select Clusters > Cloudera Management Service > Cloudera Management Service.
   • On the Status tab of the Home page, in Cloudera Management Service table, click the Cloudera Management Service link.

Starting the Cloudera Management Service

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

1. Do one of the following:
   • 1. Select Clusters > Cloudera Management Service > Cloudera Management Service.
     2. Select Actions > Start.
   • 1. On the Home page, click to the right of Cloudera Management Service and select Start.
2. Click Start to confirm. The Command Details window shows the progress of starting the roles.
3. When Command completed with n/n successful subcommands appears, the task is complete. Click Close.

Stopping the Cloudera Management Service

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

1. Do one of the following:
   • 1. Select Clusters > Cloudera Management Service > Cloudera Management Service.
     2. Select Actions > Stop.
   • 1. On the Home page, click to the right of Cloudera Management Service and select Stop.
2. Click Stop to confirm. The Command Details window shows the progress of stopping the roles.
3. When Command completed with n/n successful subcommands appears, the task is complete. Click Close.

Restarting the Cloudera Management Service

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

1. Do one of the following:
   • 1. Select Clusters > Cloudera Management Service > Cloudera Management Service.
     2. Select Actions > Restart.
   • On the Home page, click to the right of Cloudera Management Service and select Restart.
2. Click Restart to confirm. The Command Details window shows the progress of stopping and then starting the roles.
3. When Command completed with n/n successful subcommands appears, the task is complete. Click Close.

Configuring Management Service Database Limits

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

Each Cloudera Management Service role maintains a database for retaining the data it monitors. These databases (as well as the log files maintained by these services) can grow quite large. For example, the Activity Monitor maintains data at the service level, the activity level (MapReduce jobs and aggregate activities), and at the task attempt level. Limits on these data sets are configured when you create the management services, but you can modify these parameters through the Configuration settings in the Cloudera Manager Admin Console. For example, the Event Server lets you set a total number of events to store, and Activity Monitor gives you "purge" settings (also in hours) for the data it stores.

There are also settings for the logs that these various services create. You can throttle how big the logs are allowed to get and how many previous logs to retain.

1. Do one of the following:
   • Select Clusters > Cloudera Management Service > Cloudera Management Service.
   • On the Status tab of the Home page, in Cloudera Management Service table, click the Cloudera Management Service link.
2. Click the Configuration tab.
3. In the left-hand column, select the Default role group for the role whose configurations you want to modify.
4. Edit the appropriate properties:
   • Activity Monitor - the Purge or Expiration period properties are found in the top-level settings for the role.
   • Host and Service Monitor - see Data Storage for Monitoring Data.
   • Log Files - log file size settings will be under the Logs category under the role group.
5. Click Save Changes.

Adding Cloudera Navigator Roles

Minimum Required Role: Navigator Administrator (also provided by Full Administrator)

1. Do one of the following:
   • Select Clusters > Cloudera Management Service > Cloudera Management Service.
   • On the Status tab of the Home page, in Cloudera Management Service table, click the Cloudera Management Service link.
2. Click the Instances tab.
3. Click the Add Role Instances button. The Customize Role Assignments page displays.
4. Assign the Navigator role to a host.
   1. Customize the assignment of role instances to hosts. The wizard evaluates the hardware configurations of the hosts to determine the best hosts for each role. The wizard assigns all worker roles to the same set of hosts to which the HDFS DataNode role is assigned. These assignments are typically acceptable, but you can reassign them if necessary.

      Click a field below a role to display a dialog containing a list of hosts. If you click a field containing multiple hosts, you can also select All Hosts to assign the role to all hosts or Custom to display the pageable hosts dialog.

      The following shortcuts for specifying hostname patterns are supported:

      • Range of hostnames (without the domain portion)

        Range Definition	Matching Hosts
        10.1.1.[1-4]	10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4
        host[1-3].company.com	host1.company.com, host2.company.com, host3.company.com
        host[07-10].company.com	host07.company.com, host08.company.com, host09.company.com, host10.company.com

      • IP addresses
      • Rack name

      Click the View By Host button for an overview of the role assignment by hostname ranges.

5. When you are satisfied with the assignments, click Continue. The Database Setup screen displays.
6. Configure database settings:
   1. Choose the database type:
      • Leave the default setting of Use Embedded Database to have Cloudera Manager create and configure required databases. Make a note of the auto-generated passwords.
        
        
        
        
      • Select Use Custom Databases to specify external databases.
        1. Enter the database host, database type, database name, username, and password for the database that you created when you set up the database.
   2. Click Test Connection to confirm that Cloudera Manager can communicate with the database using the information you have supplied. If the test succeeds in all cases, click Continue; otherwise check and correct the information you have provided for the database and then try the test again. (For some servers, if you are using the embedded database, you will see a message saying the database will be created at a later step in the installation process.) The Review Changes screen displays.
7. Click Finish.

Deleting Cloudera Navigator Roles

Minimum Required Role: Navigator Administrator (also provided by Full Administrator)

1. Do one of the following:
   • Select Clusters > Cloudera Management Service > Cloudera Management Service.
   • On the Status tab of the Home page, in Cloudera Management Service table, click the Cloudera Management Service link.
2. Click the Instances tab.
3. Check the checkboxes next to the Navigator Audit Server and Navigator Metadata Server roles.
4. Do one of the following depending on your role:

   • Minimum Required Role: Full Administrator

     1. Check the checkboxes next to the Navigator Audit Server and Navigator Metadata Server roles.
     2. Select Actions for Selected > Stop and click Stop to confirm.

   • Minimum Required Role: Navigator Administrator (also provided by Full Administrator)

     1. Click the Navigator Audit Server role link.
     2. Select Actions > Stop this Navigator Audit Server and click Stop this Navigator Audit Server to confirm.
     3. Click the Navigator Metadata Server role link.
     4. Select Actions > Stop this Navigator Metadata Server and click Stop this Navigator Metadata Server to confirm.
5. Check the checkboxes next to the Navigator Audit Server and Navigator Metadata Server roles.
6. Select Actions for Selected > Delete. Click Delete to confirm the deletion.