Managing the Cloudera Management Service

The Cloudera Manager Management Service implements various management features as single service with a set of roles:
  • Activity Monitor - collects information about activities run by the MapReduce service
  • Host Monitor - collects health and metric information about hosts
  • Service Monitor - collects health and metric information about services and activity information from YARN and Impala services
  • Event Server - aggregates relevant Hadoop events and makes them available for alerting and for searching
  • Alert Publisher - generates and delivers alerts for certain types of events
  • Reports Manager - generates reports that provide an historical view into disk utilization by user, user group, and by directory and processing activities by user and YARN pool.
Cloudera Manager manages each role separately instead of as part of the Cloudera Manager Server for scalability (for example, on large deployments it's useful to put the monitor roles on their own hosts) and isolation.

Displaying the Cloudera Management Service Status

  1. Do one of the following:
    • Select Services > Cloudera Management Services > Cloudera Management Service, where Cloudera Management Service is the name of the Cloudera management service.
    • On the Status tab of the Home page, in Cloudera Management Services table, click the Cloudera Management Service link.

Starting the Cloudera Management Service

  1. Do one of the following:
      1. Select Services > Cloudera Management Services > Cloudera Management Service, where Cloudera Management Service is the name of the 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

  1. Do one of the following:
      1. Select Services > Cloudera Management Services > Cloudera Management Service, where Cloudera Management Service is the name of the 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.

Configuring Management Service Database Limits

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 you want to store. Host Monitor and Service Monitor let you set data expiration thresholds (in hours), 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 Services > Cloudera Management Services > Cloudera Management Service, where Cloudera Management Service is the name of the Cloudera management service.
    • On the Status tab of the Home page, in Cloudera Management Services table, click the Cloudera Management Service link.
  2. Select Configuration > View and Edit.
  3. In the left-hand column, select the Default role group for the role whose configurations you want to modify.
  4. For some services, such as the Activity Monitor, Service Monitor, or Host Monitor, the purge or expiration period properties are found in the top-level settings for the role. Typically, Log file size settings will be under the Logs category under the role group.