Splunk Search

Why is only one member of a search head cluster reporting "Maximum number of concurrent searches has been reached"?

pkeller
Contributor

Recently started encountering issues where one node of a 4 node search head cluster starts reporting:

   SHPMaster - Search not executed: Your maximum number of concurrent searches has been reached. usage=93 quota=40 user=my.username

The strange thing is that this is only happening on one node. The Activity->Jobs drop-down doesn't reveal anywhere close to the number of running jobs ... and subsequently, bouncing splunkd on the reporting member resolves the issue ... ( and it gradually reappears over the next 5-7 days )

This environment was recently upgraded to 6.3.2.

I guess the question then would be, 'why is this happening only on a single node?'

0 Karma

splunkIT
Splunk Employee
Splunk Employee

The node reporting this issue must be the the captain node at the time, as the channel reporting the message is SHPMaster. This message is related to a known search head clustering bug introduced in 6.3. Please refer to this post for details:

https://answers.splunk.com/answers/337598/search-head-cluster-pre-63-we-could-run-more-numbe-2.html

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...