Managing Pepperdata Services

Procedure

1. Start the Pepperdata Collector.

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

   • sudo service pepcollectd start
   • sudo systemctl start pepcollectd

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.

2. Start the PepAgent.

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

   • sudo service pepagentd start
   • sudo systemctl start pepagentd

   If the service successfully starts, the Pepperdata Version [VERSION-STRING] OK message appears in the /var/log/pepperdata/pepagent/pepagent.log file.

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.

Procedure

• In Cloudera Manager, select the Start action for the Pepperdata service.

Procedure

1. Open a command shell (terminal session) and log in to the host as a user with sudo privileges.

2. Start the Pepperdata Collector.

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

   • sudo service pepcollectd start
   • sudo systemctl start pepcollectd

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.

3. Start the PepAgent.

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

   • sudo service pepagentd start
   • sudo systemctl start pepagentd

   If the service successfully starts, the Pepperdata Version [VERSION-STRING] OK message appears in the /var/log/pepperdata/pepagent/pepagent.log file.

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.

(For Supervisor versions earlier than 8.x) To trigger the Supervisor to load configuration changes, refresh the YARN ResourceManager configuration.

Procedure

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

• (YARN 2) Load the new configuration: in Cloudera Manager, select the Refresh action for the ResourceManager.

• (For YARN 3, you do not need to manually load the new configuration because the PepAgent automatically forwards it to the capacity monitor.)

Procedure

1. From the command line, copy the Pepperdata bootstrap script that you extracted from the Pepperdata package from its local location to any location; in the following examples, we’ve copied it to /tmp.

   • For Amazon EMR clusters:

     aws s3 cp s3://<pd-bootstrap-script-from-install-packages> /tmp/bootstrap

   • For Google Dataproc clusters:

     sudo gsutil cp gs://<pd-bootstrap-script-from-install-packages> /tmp/bootstrap

2. Load the revised configuration by running the Pepperdata bootstrap script.

   • For EMR clusters:

     • You can use the --long-options form of the --bucket, --upload-realm, and --is-running arguments as shown or their -short-option equivalents, -b, -u, and -r.

     • The --is-running (-r) option is required for bootstrapping an already-running host prior to Supervisor version 7.0.13.

     • Optionally, you can specify a proxy server for the AWS Command Line Interface (CLI) and Pepperdata-enabled cluster hosts.

       Include the --proxy-address (or --emr-proxy-address for Supervisor version 8.0.24 or later) argument when running the Pepperdata bootstrap script, specifying its value as a fully-qualified host address that uses https protocol.

     • If you’re using a non-default EMR API endpoint (by using the --endpoint-url argument), include the --emr-api-endpoint argument when running the Pepperdata bootstrap script. Its value must be a fully-qualified host address. (It can use http or https protocol.)

     • If you are using a script from an earlier Supervisor version that has the --cluster or -c arguments instead of the --upload-realm or -u arguments (which were introduced in Supervisor v6.5), respectively, you can continue using the script and its old arguments. They are backward compatible.

     • Optionally, you can override the default exponential backoff and jitter retry logic for the describe-cluster command that the Pepperdata bootstrapping uses to retrieve the cluster’s metadata.

       Specify either or both of the following options in the bootstrap’s Optional arguments. Be sure to substitute your values for the <my-retries> and <my-timeout> placeholders that are shown in the command.

       • max-retry-attempts—(default=10) Maximum number of retry attempts to make after the initial describe-cluster call.

       • max-timeout—(default=60) Maximum number of seconds to wait before the next retry call to describe-cluster. The actual wait time for a given retry is assigned as a random number, 1–calculated timeout (inclusive), which introduces the desired jitter.

   # For Supervisor versions before 7.0.13:
   sudo bash /tmp/bootstrap --bucket <bucket-name> --upload-realm <realm-name> --is-running [--proxy-address <proxy-url:proxy-port>] [--emr-api-endpoint <endpoint-url:endpoint-port>] [--max-retry-attempts <my-retries>] [--max-timeout <my-timeout>]
      
   # For Supervisor versions 7.0.13 to 8.0.23:
   sudo bash /tmp/bootstrap --bucket <bucket-name> --upload-realm <realm-name> [--proxy-address <proxy-url:proxy-port>] [--emr-api-endpoint <endpoint-url:endpoint-port>] [--max-retry-attempts <my-retries>] [--max-timeout <my-timeout>]
      
   # For Supervisor versions 8.0.24 and later:
   sudo bash /tmp/bootstrap --bucket <bucket-name> --upload-realm <realm-name> [--emr-proxy-address <proxy-url:proxy-port>] [--emr-api-endpoint <endpoint-url:endpoint-port>] [--max-retry-attempts <my-retries>] [--max-timeout <my-timeout>]
   

   • For Dataproc clusters:

     sudo bash /tmp/bootstrap <bucket-name> <realm-name>

   The script finishes with a Pepperdata installation succeeded message.

Procedure

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

   • sudo service pepagentd stop
   • sudo systemctl stop pepagentd

2. Stop the Pepperdata Collector. You can use either the service (if provided by your OS) or systemctl command:

   • sudo service pepcollectd stop
   • sudo systemctl stop pepcollectd

3. (Only if running PepMetrics; otherwise not applicable.
   Do not restart PepMetrics because it is now unsupported and unneeded.)

   1. Stop the PepMetrics agent.

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

      • sudo service pepmetricsd stop
      • sudo systemctl stop pepmetricsd

   2. Disable the PepMetrics agent.

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

      • sudo chkconfig pepmetricsd off
      • sudo systemctl disable pepmetricsd

Procedure

• In Cloudera Manager, select the Stop action for the Pepperdata service.

Procedure

1. Open a command shell (terminal session) and log in to the host as a user with sudo privileges.

2. Stop the PepAgent.

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

   • sudo service pepagentd stop
   • sudo systemctl stop pepagentd

3. Stop the Pepperdata Collector.

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

   • sudo service pepcollectd stop
   • sudo systemctl stop pepcollectd

Procedure

1. Restart the Pepperdata Collector.

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

   • sudo service pepcollectd restart
   • sudo systemctl restart pepcollectd

2. Restart the PepAgent.

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

   • sudo service pepagentd restart
   • sudo systemctl restart pepagentd

Procedure

• In Cloudera Manager, select the Restart action for the Pepperdata service.

Procedure

1. Open a command shell (terminal session) and log in to an already-running host as a user with sudo privileges.

2. Restart the Pepperdata Collector.

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

   • sudo service pepcollectd restart
   • sudo systemctl restart pepcollectd

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.

3. Restart the PepAgent.

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

   • sudo service pepagentd restart
   • sudo systemctl restart pepagentd

   If the service successfully restarts, the Pepperdata Version [VERSION-STRING] OK message appears in the /var/log/pepperdata/pepagent/pepagent.log file.

   If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.