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!

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...

Splunk New Course Releases for a Changing World

Every day, the world feels like it’s moving faster with new technological breakthroughs, AI innovation, and ...

Insights from .conf 2025, Smart Edge Processor Scaling, and a New Splunk Lantern ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...