Some Pepperdata products can be individually disabled, while other products are always on as long as Pepperdata is running. This section includes procedures for all the products that can be individually disabled, and explains their interdependencies.

Uninstall All Pepperdata Products

To uninstall all Pepperdata products and functions, perform the configuration and installation procedures in reverse.

Use the distribution-specific configuration and installation documentation as a guide. More explicit instructions cannot be provided because the actual configuration you implemented during the installation and configuration steps is unique to your environment. If you need help, contact Pepperdata Support.

Disable Capacity Optimizer

Capacity Optimizer operates (is enabled) on a percentage of the hosts in the cluster as defined by the pepperdata.supervisor.splitTest.percent property value. To disable Capacity Optimizer, reset this property value to zero, and load the configuration change by refreshing the YARN ResourceManager configuration.

Procedure

1. In pepperdata-site.xml, reset the pepperdata.supervisor.splitTest.percent property to 0.

   <property>
     <name>pepperdata.supervisor.splitTest.percent</name>
     <value>0</value>
   </property>
   

2. Load the configuration change.

   Procedure

To trigger the Supervisor to load configuration changes, refresh the YARN ResourceManager configuration.

sudo yarn rmadmin -refreshQueues

Disable Application Profiler

Procedure

1. In the in the MapReduce Job History Server host’s Pepperdata configuration file, pepperdata-config.sh, change the PD_JOBHISTORY_MONITOR_ENABLED environment variable’s value to 0.

   export PD_JOBHISTORY_MONITOR_ENABLED=0

2. Restart the PepAgent on the MapReduce Job History Server host.

   You can use either the service (if provided by your OS) or systemctl command:

   • sudo service pepagentd restart
   • sudo systemctl restart pepagentd

Disable Monitoring

To disable monitoring across the cluster, stop the Pepperdata PepAgent on every host.

You can use either the service (if provided by your OS) or systemctl command:

• sudo service pepagentd stop
• sudo systemctl stop pepagentd

After a host’s NodeManager cache of the PepAgent state is cleared (typically about five minutes), new containers that are launched do not include Pepperdata.

(When you restart PepAgent, it takes about five minutes for new containers that are launched to include Pepperdata.)

Disable Metrics Uploading

To stop uploading the collected metrics to the Pepperdata dashboard, stop the Pepperdata Collector on every host.

Pepperdata continues to collect the metrics so that they’re available for viewing and analysis when you resume the pepcollectd process.

You can use either the service (if provided by your OS) or systemctl command:

• sudo service pepcollectd stop
• sudo systemctl stop pepcollectd