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!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...