Splunk Enterprise

How to solve the problem related to indexing after version upgrade

jjeongeunida
Engager

I received red alarms from health status.
The types of alarm vary over time.
but the warnings that continuously occur are Ingestion Latency, IOWait, Searches Delayed, etc.

And the Detail message displays 'Splunkd's processing queue is full.'
Is there any way to check which process is in the queue?
OR is there a way to flush the queue?

I increased CPU and memory, but the problem was not solved.
And I recently upgraded the Splunk version from 8.1.4 to 9.0.2.

Thank you.

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Ingestion latency might be a "feature" of your setup in certain cases (like big periodically created - for example, rsynced from remote location - files and low thruput limit).

IOwait is, as @richgalloway said, a known false positive.

Searches delayed is typically an issue with your workload and/or definition of your searching schedules.

Apart from IOwait they should not be connected with your upgrade.

richgalloway
SplunkTrust
SplunkTrust

The  IOWait warning is a known false positive.  You can adjust it to turn red with a higher IOWait value.

The Monitoring Console will display the indexer queues at Indexing->Performance->Indexing Performance: Instance

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Infographic provides the TL;DR for the 2024 Splunk Career Impact Report

We’ve been buzzing with excitement about the recent validation of Splunk Education! The 2024 Splunk Career ...

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...