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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...