Known issues for DSP

This version of the Splunk Data Stream Processor has the following known issues and workarounds.

If no issues appear here, no issues have yet been reported.

Date filed	Issue number	Description
2021-10-05	DSPOP-4205	Pulsar connector: When you create a connection to Apache Pulsar, the server_ca_certificate argument is labeled as optional but is required. If you leave this field blank, pipeline activation fails with error "Failed to fetch". Workaround: Edit the Pulsar connection and upload the original CA certificate.
2021-05-26	DSPOP-5293	Multi node clusters do not work on certain RHEL versions running on VMWare Workaround: A regression introduced into the RHEL 8.3 linux kernel prevents multi node DSP clusters from working properly on VMWare infrastructure when the DSP VMs are scheduled across multiple ESX hosts. This regression also exists in RHEL 8.6. To workaround, disable checksum offloading for impacted DSP network interfaces. ethtool -K cni0 tx off ethtool -K flannel.1 tx off Note: this must be run on every node in the cluster and every system boot. The system should recover within a few minutes. More information about the nature of the issue is found at https://access.redhat.com/solutions/5881451
2020-05-06	DSPOP-4213	Custom UI for the Select function does not work when the incoming data schema contains a field name that requires single quotes. Workaround: 1. Click on the SPL expressions table at the top right corner of the select function's configuration panel. 2. Input the field names with/without quotes into the editor box as valid SPL statements like 'offset' as kafka_offset. 3. Multiple entries could be added by the add button below.
2020-04-21	DSPOP-4214	You cannot switch between the Canvas and the SPL Builder if the functions are not configured correctly. Workaround: Configure every function so that the UPL is valid.