Installing Pepperdata (CDH and CDP Private Cloud Base)

To install Pepperdata via a parcel for Cloudera Data Platform (CDP) Private Cloud Base, first install the parcel for your distro/environment; next, open up listen ports as necessary; and then, optionally, reconfigure Pepperdata properties for settings such as Unix utility command locations.

Task 1: Install the Pepperdata Software

Prerequisite

Creation of the pepperdata user and pepperdata log directories uses the CM Agent, a CM Component, at the time of parcel activation and at the time of adding the pepperdata service. Each of these operations requires the CM agent to run as the root user. This requires one of the following permissions during the initial CM installation:

• Access to the root user account using a password or SSH key file.

• Passwordless sudo access for a specific user.

Procedure

1. Download the following artifacts from the Downloads page to any local directory, and copy them to the Cloudera Manager Server.

   • The appropriate PepperdataSupervisor parcel for your distro; see Downloads: CDP Private Cloud Base and CDP Public Cloud or Downloads: CDH.
   • The latest pepperdata-csd-X.Y.Z.tgz CSD (custom service descriptor) for Supervisor 8.1; see Downloads: CDP Private Cloud Base and CDP Public Cloud or Downloads: CDH.

2. Extract the contents of the TGZ archives and move the files as follows:

   • Move the parcel (the *.parcel file) and corresponding SHA checksum file (*.parcel.sha) to the /opt/cloudera/parcel-repo directory.
   • Move the CSD JAR file to the /opt/cloudera/csd directory.

3. Restart the Cloudera Service and Configuration Manager (SCM) server (service: cloudera-scm-server).

   Note: Restarting the SCM server is not the same as restarting the Cloudera Management Service by using the Cloudera Manager interface. Unless you use the command line to explicitly restart the SCM server (the cloudera-scm-server service), you will be unable to use Cloudera Manager to add the Pepperdata service.

   service cloudera-scm-server restart

   After the restart, the new parcels and the Pepperdata service (in the CSD JAR file) are available for activation.

4. In Cloudera Manager, distribute and activate the Pepperdata Supervisor parcel—the *.parcel file.

Task 2: Add Pepperdata Service to Cloudera Manager

Use Cloudera Manager to perform this procedure, which adds the Pepperdata service and the custom service descriptor (CSD) to the Cloudera Manager environment.

1. Select your cluster, click Actions > Add Service, in the Service Type column, select Pepperdata, and click Continue.

2. Select Dependencies page.

   • (Kerberized clusters) If the core services of the ResourceManagers and the MapReduce Job History Server are Kerberized (secured with Kerberos), select Optional Dependencies. (The YARN dependency is required so that Pepperdata can fetch YARN-related values to use for the Pepperdata configuration.)

   • (Clusters without Kerberos) Select No Optional Dependencies.

3. Assign Roles page. Customize the Role Assignments:

   • Click PepAgent, select all hosts, and click OK.
   • Click Supervisor, select all the ResourceManager hosts, click OK, and click Continue.
   Do not assign the PepMetrics role. It is now unsupported and unneeded.

4. In the Review Changes page, enter your custom information.

   1. For the Pepperdata License Specification, enter data:// and then (without any additional spaces) the contents of the license file that we emailed you. If the data:// string is already shown, do not enter it a second time.

   2. For the Pepperdata Dashboard Cluster Realm Name, enter the cluster name exactly as shown in the license email. Be sure to use the same capitalization.

   3. (Non-Hadoop Clusters) If you’re installing Pepperdata on a cluster without Hadoop, such as a Kafka-only cluster for Streaming Spotlight, the Pepperdata PepAgent must be configured to run without Hadoop.

      If you’re installing Pepperdata in a cluster that has Hadoop, skip this substep. If you perform this substep in a Hadoop cluster, Pepperdata will not operate correctly.

      Locate the Run Pepperdata in Non-Hadoop Environment parameter, and select it.

   4. (Kerberized clusters) If the core services of the ResourceManagers and the MapReduce Job History Server are Kerberized (secured with Kerberos), locate the Enable Access to Kerberized Cluster Components parameter, and ensure that it is selected.

      • Newer versions of Cloudera Manager automatically detect that Kerberos is enabled on a cluster. In this case, the option will already be selected, and you must be careful to not cancel the option by selecting (clicking) it again.

      • Older versions of Cloudera Manager do not detect that Kerberos is enabled, so you must select this option.

   5. Click Continue.

5. Complete the steps as prompted by the Add Service wizard, all the way through (and including) clicking Finish.

Next: Configuring Pepperdata