Upgrade the Data Stream Processor

If the Splunk Data Stream Processor was previously installed and configured, do the following to upgrade your software. Review these two known issues before upgrading:

An upgrade to DSP 1.1.0 changes the message bus from Apache Kafka to Apache Pulsar. Data sent before and during the upgrade is lost in the switchover. You may continue sending data during the upgrade, but only data ingested after the upgrade finishes will be sent through DSP.

If you are currently using DSP 1.0.0, you cannot directly upgrade to DSP 1.1.0. You must first upgrade DSP 1.0.0 to DSP 1.0.1, and then upgrade again to DSP 1.1.0.

Steps

1. Download the new Data Stream Processor tarball on the master node of your cluster.
2. Extract the tarball.

   tar xf <dsp-version>.tar

3. (Optional) copy and extract the tarball on each DSP node in your cluster. This lets you make changes on each node if required during the upgrade process even if the master node is down or unavailable.
4. Navigate to the extracted file on your master node.

   cd <dsp-version>

5. (Optional) If your environment has a small root volume (6GB or less of free space) in /tmp, your upgrade may fail when you run out of space. Choose a different directory to write temporary files to during the upgrade process.

   export TMPDIR=/<directory-on-larger-volume>

6. From the extracted file directory, run the upgrade script.

   ./upgrade

7. Upgrading can take a while. Upon completion, the following message is shown.

   Waiting for DSP to startup
   ....................
   DSP startup completed
   

8. (Optional) While waiting for the upgrade to complete, you can use the following command to monitor the progress of your upgrade. Run this command after you see the Waiting for DSP to startup message.

   kubectl get pods -n dsp
   

   When the following services have status RUNNING, then the upgrade is complete: dsp, ingest-hec, ingest-s2s, splunk-streaming-rest, usr-mgmt-svc.