Splunk® Data Stream Processor

Install and administer the Data Stream Processor

On April 3, 2023, Splunk Data Stream Processor reached its end of sale, and will reach its end of life on February 28, 2025. If you are an existing DSP customer, please reach out to your account team for more information.

All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 in order to continue to receive full product support from Splunk.
This documentation does not apply to the most recent version of Splunk® Data Stream Processor. For documentation on the most recent version, go to the latest release.

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.

Remove (leave) all nodes from the cluster

To uninstall DSP, first remove all nodes from the cluster. From the working directory of a node, use the leave command. Repeat on each node.

dsp leave

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	k0s has been successfully uninstalled

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

Last modified on 26 April, 2024
Upgrade the Splunk Data Stream Processor on the Google Cloud Platform   Cross-Origin Resource Sharing Policy

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2, 1.4.3

Was this topic useful?

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