Splunk Search

This usually indicates problems with underlying storage performanc

Alnardo
Engager


[serversindex] Configuration initialization for /opt/splunk/var/run/searchpeers/serverhead-1721913866 took longer than expected (1002ms) when dispatching a search with search ID remote_serverhead_userxx__userxx__search__search1_1723144245.50. This usually indicates problems with underlying storage performance.

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @Alnardo ,

which type of disks are you using for your Search Head and your Indexers?

how many IOPS have your disks?

remember that Splunk requires at least 800 IOPS and if you have more performat disks you'll have more performat searches.

For more infos see at https://docs.splunk.com/Documentation/Splunk/9.3.0/Capacity/Referencehardware

Ciao.

Giuseppe

isoutamo
SplunkTrust
SplunkTrust
This could be storage performance issue or it could be that your environment is too small for your workload.
As said, 1st you should check storage performance and if it’s enough then look from you MC (monitoring console) other resource usage etc.
0 Karma

isoutamo
SplunkTrust
SplunkTrust
And the question is?
0 Karma

Alnardo
Engager

How can I solve that?

0 Karma
Get Updates on the Splunk Community!

See Splunk Platform & Observability Innovations at Cisco Live EMEA

Hi Splunkers, Learn about what’s next for Splunk Platform at Cisco Live EMEA.  Data silos are a big challenge ...

The OpenTelemetry Certified Associate (OTCA) Exam

What’s this OTCA exam? The Linux Foundation offers the OpenTelemetry Certified Associate (OTCA) credential to ...

From Manual to Agentic: Level Up Your SOC at Cisco Live

Welcome to the Era of the Agentic SOC   Are you tired of being a manual alert responder? The security ...