Cloudera Docs

Managing your Cloudera Observability On-Premises purge event

Steps for updating, stopping, and troubleshooting your Cloudera Observability On-Premises Purge event.

The following management tasks can be performed:

Updating your Cloudera Observability On-Premises purge event

To update your purge event:

  1. In a supported web browser, log in to Cloudera Manager as a user with full system administrator privileges.
  2. From the Navigation panel, select Clusters and then OBSERVABILITY.
  3. From the Status Summary panel, select Admin API Server.
  4. Click the Configuration tab.
  5. Search for the Admin API Server Advanced Configuration Snippet (Safety Valve) for the observability-conf/sigmaadminapi.properites option field.
  6. In the text field, change the required values.
  7. Click Save Changes.
  8. From the Actions menu, select Restart this Admin API Server.
  9. In the Restart this Admin API Server message, confirm your changes by clicking Restart this Admin API Server.
  10. When the Restart API Server step window displays Completed, click Close.

Stopping the Cloudera Observability On-Premises purge event

You can stop a recurring purge event or stop a scheduled purge event whilst still running.

  • To stop a recurring purge event:
    1. In a supported web browser, log in to Cloudera Manager as a user with full system administrator privileges.
    2. From the Navigation panel, select Clusters and then OBSERVABILITY.
    3. From the Status Summary panel, select Admin API Server.
    4. Click the Configuration tab.
    5. Search for the Admin API Server Advanced Configuration Snippet (Safety Valve) for the observability-conf/sigmaadminapi.properites option field.
    6. In the text field, replace the blobstore.purger.frequency value with none.
    7. Click Save Changes.
    8. From the Actions menu, select Restart this Admin API Server.
    9. In the Restart this Admin API Server message, confirm your changes by clicking Restart this Admin API Server.
    10. When the Restart API Server step window displays Completed, click Close.
  • To stop a scheduled purge event whilst still running:
    1. In a supported web browser, log in to Cloudera Manager as a user with full system administrator privileges.
    2. From the Navigation panel, select Clusters and then OBSERVABILITY.
    3. From the Status Summary panel, select Admin API Server.
    4. From the Actions menu, select Stop this Admin API Server.
    5. Still in the Admin API Server page, click the Configuration tab.
    6. Search for the Admin API Server Advanced Configuration Snippet (Safety Valve) for the observability-conf/sigmaadminapi.properites option field.
    7. Replace the blobstore.purger.frequency value with none.
    8. Click Save Changes.
    9. From the Actions menu, select Restart this Admin API Server.
    10. In the Restart this Admin API Server message, confirm your changes by clicking Restart this Admin API Server.
    11. When the Restart API Server step window displays Completed, click Close.

Troubleshooting

The Cloudera Observability On-Premises purge event does not delete directories and files that do not have the full observability owner and file permissions. Files and directories may revert back to the hdfs owner when a restore is created from a snapshot. In this case and before creating an automatic or manual purge event you must verify the owner and file permissions of the required files to be purged.

To reset your HDFS files and directories as the observability owner with full administrative permissions do the following:
  1. In a terminal go to the /etc directory and open the hdfs password file by entering:

    vim passwd

  2. Search for the kafka parameter.
  3. Replace /sbin/nologin with /bin/hash.
  4. Save the file.
  5. Grant full observability access permissions to the hdfs password file by using the chown command.

Tracking your purge event from log entries

You can determine if the purge event was successful or identify potential problems from the Cloudera Manager Admin API Server log files.

The Admin API Server log file entries also list the names of the files and directories that were deleted and provide details about how many files and directories were deleted, the sum total size of the files and directories that were deleted, and the time they were deleted.