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-12-03 | DSP-43606 | Server can be attacked by slow clients during TLS handshake |
2021-08-04 | DSP-41040 | Checkpoint cleanup for pull-based connectors cause performance issues. |
2021-06-01 | DSP-38591 | Subseconds are not sent to Firehose |
2021-02-23 | DSP-34031 | In HEC sink, unhandled exception causes pipeline restarts |
2020-12-15 | DSP-31160 | HEC sink leaks memory when ACK is disabled |
2020-02-10 | DSP-17563 | Unable to upgrade a DSP cluster if the hosts have 6GB or less of free space on the root volume Workaround: Choose a different directory to write temporary files to during the upgrade process. Run the following command in your cluster. export TMPDIR=/<directory-on-larger-volume> |
2019-11-08 | DSP-14655 | After updating UI cert and deploying, nginx did not automatically restart. Workaround: Manually delete the dsp-reverse-proxy pod, and it will pick up the new configuration. |
2019-11-05 | DSP-14507 | Unable to launch pods due to "cannot allocate memory" caused by leaked cgroups Workaround: If your host system is running systemd v231 or earlier (generally centos7 or rhel7), there is a bug where cgroup resources are not cleaned up. This error manifests as the following on pod creation: Warning FailedCreatePodContainer 3s (x2 over 15s) kubelet, 1.2.3.4 unable to ensure pod container exists: failed to create container for [kubepods ...] : mkdir /sys/fs/cgroup/memory/kubepods/...: cannot allocate memory Workaround 1: Upgrade systemd to v232 or later Workaround 2: Add the following kernel parameter and reboot the affected machines: grubby --args=cgroup.memory=nokmem --update-kernel /boot/vmlinuz-<kernel_image> Replace <kernel_image> as appropriate for your kernel. |
2019-10-30 | DSP-14699, SCP-18898 | scloud ingest post-metrics command does not work Workaround: Use cURL to ingest metrics events instead. |
2019-09-30 | DSP-13537 | Flink checkpoint files do not get cleaned up in Minio |
2019-07-16 | DSP-11196 | Binary values are incorrectly represented as Base64 Workaround: Preview will display binary data as Base64-encoded strings. If the data is a string type that is Base64-encoded, the icon at the top of the column will have a lower-case "a" displayed. If the data is a bytes type, the icon at the top of the column will have a capital "B" displayed. This data is Base64-encoded so users may take that data and decode it back to raw bytes for further inspection. |
2019-05-31 | DSP-8731 | DSP does not yet support LZ4 compression in reads and writes to Kafka |
2019-04-16 | DSP-7430 | Events forwarded from DSP to the Splunk platform with timestamp of 0 are indexed with _time of Jan 1, 1970 Workaround: Make sure that your DSP timestamp is not 0 |
Fixed issues for DSP | Third-party credits in Splunk DSP |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.0.1
Feedback submitted, thanks!