All Apps and Add-ons

Error in 'databasePartitionPolicy': Max Raw Size Limit Exceeded

jjozwik702
Explorer

Getting Error in 'databasePartitionPolicy': Max Raw Size Limit Exceeded on the overview page of the modsecurity app when I switch to longer timeframes.

My modsecurity audit log is about 220 megs.

Anyone know what this error means and how to fix it? Haven't been able to find anything regarding the Raw Size Limit..

rsimmons
Splunk Employee
Splunk Employee

This is a known issue (SPL-93527) where search process consumes some memory and throws the following error databasePartitionPolicy - Max Raw Size Limit Exceeded

The temporary workaround for this issue is to disable the BatchSearches:
limits.conf:
[search]
allow_batch_mode = false

jjozwik702
Explorer

Additionally the server RAM spikes out when viewing most any of the overview pages.

0 Karma

jjozwik702
Explorer

From splunkd.log

06-18-2014 18:43:45.010 +0000 WARN ProcessDispatchedSearch - PROCESS_SEARCH terminate called after throwing an instance of 'std::bad_alloc'
06-18-2014 18:43:45.010 +0000 WARN ProcessDispatchedSearch - PROCESS_SEARCH what(): std::bad_alloc

Memory jumps way up.
Wondering if this should run in concurrent mod instead.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...