Splunk Search

Splunk Message : Search has been terminated. This is most likely due to an out of memory condition

Naveen_4025
New Member

Hello Everyone,
I'm attempting to search for queries in Splunk Free Edition. However, it worked well for some time, and then I got the error "Search has been terminated." This is most likely due to a lack of recollection." This occurs rather frequently. I created a free AWS instance using the Linux platform. Please suggest any solutions for these problems. (I've included a screenshot for reference.)

Error.png 

0 Karma

richgalloway
SplunkTrust
SplunkTrust

How much memory does the AWS instance have?  It should have at least 12GB.

It's possible your search query is too memory-intensive.  Use the fields command to remove unused fields and save memory.  Share the query so we can offer other suggestions to reduce memory use.

---
If this reply helps you, Karma would be appreciated.
0 Karma

Naveen_4025
New Member

Hello.

Thank you for response.  I think it's 8GB. If I increase the memory will I be charged on AWS account?

Secondly, how can we save up the memory usage in my Splunk Console ?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

I'm not an AWS expert, but increasing the amount of memory on the instance probably will incur additional cost.

The Monitoring Console (MC) should show how much memory searches are using.  In the MC, go to Resource Usage->Resource Usage: Instance

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...