Splunk Search

Error: mvexpand output will be truncated due to excessive memory usage

erstexas
Path Finder

I get the above error when running a query. I have increased the RAM and swap space on the system and I still get the error. Are there internal controls for this that I could adjust? I can confirm that Splunk is nowhere near running out of memory and not sure how to fix this so that the results are not truncated.

Tags (3)
1 Solution

khourihan_splun
Splunk Employee
Splunk Employee

Howdy Tex!

Check out http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Limitsconf and check out the max_mem_usage_mb = setting.

You can increase the size to handle larger mvexpand results. Just be sure to make sure you have enough free RAM for the size you choose.

best,
Kyle

View solution in original post

khourihan_splun
Splunk Employee
Splunk Employee

Howdy Tex!

Check out http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Limitsconf and check out the max_mem_usage_mb = setting.

You can increase the size to handle larger mvexpand results. Just be sure to make sure you have enough free RAM for the size you choose.

best,
Kyle

erstexas
Path Finder

You know, I actually looked through that file and didn't see anything that sounded interesting to fix this. I did not find the above online doc listing it as an optional setting. Thanks. I will experiment with this setting.

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

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