Pepperdata pepper logo
Support Logout

Upgrading a Cluster (RPM/DEB)

Upgrading a cluster can entail upgrading the Hadoop distribution, upgrading Pepperdata, or upgrading both Hadoop and Pepperdata. For supported Pepperdata upgrade paths, you can skip Pepperdata versions without having to perform intermediate upgrades, and you can rollback a Pepperdata upgrade to your previously installed version. In accordance with best practices for upgrades, we recommend that you first upgrade a test cluster and verify successful operation before you upgrade a production cluster.

On This Page

When to Upgrade Pepperdata

To decide whether to upgrade Pepperdata, consider whether:

  • There are new features that you’d like to use.

  • There are bug fixes that are applicable to your environment. (See Pepperdata Release Notes.)

  • You want to upgrade your cluster’s Hadoop distribution to a version that is not supported by your installed Pepperdata version but that a newer Pepperdata version supports. (See Pepperdata-Platform Support.)

  • You need assistance, but your version of Pepperdata is no longer supported. (For the list of supported versions, see Pepperdata-Platform Support.)

Quick Start for Upgrading Pepperdata

The steps in the quick start procedure are high-level, general instructions.

Supported Pepperdata upgrade paths: from any earlier Pepperdata 6.x version

If you’re upgrading from any Pepperdata v5.x version, contact Pepperdata Support.

Click the tab for your Pepperdata installation and cluster manager—RPM/DEB Package or Parcel for Cloudera—and perform the procedure.

  • RPM/DEB Package

    • Procedure

    1. Upgrade the Pepperdata package.

    2. Merge the contents of the new Pepperdata configuration file template, /etc/pepperdata/pepperdata-config.sh-template, into your existing Pepperdata configuration file, /etc/pepperdata/pepperdata-config.sh.

    3. If pepmetricsd was previously enabled, disable it. (PepMetrics is now unsupported, and will be removed in a future Supervisor release.)

    4. Restart the pepagentd and pepcollectd services.

    5. Restart YARN and, if monitoring HBase, perform a rolling restart of the HBase RegionServers.

  • Parcel for Cloudera

    • Procedure

    1. Stop the Pepperdata services.

    2. If pepmetricsd was previously enabled, disable it. (PepMetrics is now unsupported, and will be removed in a future Supervisor release.)

    3. Stop the YARN services.

    4. Deactivate the old Pepperdata Supervisor Parcel.

    5. Install and activate the new Pepperdata Supervisor Parcel.

    6. Restart the YARN services and, if monitoring HBase, perform a rolling restart of the HBase RegionServers.

    7. (If using Query Spotlight) On every Hive server, restart the hiveserver2 service.

    8. Restart the Pepperdata services.

Detailed Upgrade and Rollback Procedures

For detailed upgrade and rollback procedures, see the following: