Splunk® Data Stream Processor

Install and administer the Data Stream Processor

Acrobat logo Download manual as PDF


DSP 1.2.1 is impacted by the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities from Apache Log4j. To fix these vulnerabilities, you must upgrade to DSP 1.2.2-patch02. See Upgrade the Splunk Data Stream Processor from 1.2.1 to 1.2.2-patch02 for upgrade instructions, and Splunk Security Advisory for Apache Log4j (CVE-2021-44228 and CVE-2021-45046) for more information.
Acrobat logo Download topic as PDF

Uninstall the Splunk Data Stream Processor

Once you uninstall the Splunk Data Stream Processor (DSP), you can perform a clean reinstallation. See Install the Data Stream Processor in this manual.

The following instructions assume that you have system administrator (root) permissions. If you do not have root permissions, you can use the sudo command to run the necessary scripts required to uninstall DSP.

Step 1: Remove (leave) all nodes from the cluster

To uninstall DSP, first remove all nodes from the cluster.

  1. From the working directory of a node, use the leave command. Repeat on each node.
    ./leave
  2. Once you only have one node left in your cluster, force the leave command to run.
    ./leave --force 

Once the last node leaves the cluster, the uninstall process kicks off. You'll see the following output once complete.

Thu Jun 18 14:41:53 UTC	Gravity has been successfully uninstalled

Depending on the state of your cluster, the uninstall process could take up to several hours to complete.

Step 2: Remove Gravity

After removing all nodes from the cluster, clean up the Gravity directory.

Run the following from the working directory:

rm -rf gravity/.gravity

After you've completed both steps, you can now perform a clean reinstallation of DSP.

Last modified on 10 November, 2020
PREVIOUS
Upgrade the Splunk Data Stream Processor from 1.2.0 to 1.2.1
  NEXT
Secure the DSP cluster with SSL/TLS certificates

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.1.0, 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02


Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters