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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...

Deep Dive: Optimizing Telemetry Pipelines in Splunk Observability Cloud

In this session, we will peel back the layers of Splunk Observability Cloud’s cost-optimization features. ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...