Deployment Architecture

Why did our search head crash? and how can we prevent it?


Our search head crashed, saying -

-- Apr 23 09:00:35 kernel: Out of memory: Kill process 2137 (splunkd) score 162 or sacrifice child

Two instances of the TA-check-point-app-for-splunk ran - one for 21 minutes consuming 21 GBs of memory and the other for 11 minutes, consuming 11 GBs.

How can we put safe-guards to prevent it?

Labels (1)
0 Karma


The SH crashed because the OS killed it for using too much memory.

One solution is to add more memory to the SH, but that may be a short-term fix.

More important than knowing which apps were running at the time is knowing which searches were running at the time. Once you know that you can take steps to prevent future crashes, such as:

  • Make the searches more efficient
  • Schedule the searches so they don't run at the same time.
If this reply helps you, an upvote would be appreciated.


We decided to use the enable_memory_tracker feature as in How can I generate a search which uses lots of memory?

0 Karma
Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...