Getting Data In

index settings using "auto" - what is my bucket size?

cpenkert
Path Finder

We are on 4.05 and are using the default of memPoolMB = auto in indexes.conf. Is there a way I can find out what size is being set via "auto"?

Tags (1)
1 Solution

the_wolverine
Champion

Actually, memPoolMB is not related to bucket size, but memory pool allocation.

maxDataSize determines the size of your buckets. On 64-bit architecture, a setting of auto_high_volume will give you a bucket size of 10GB. On 32-bit, this is 750MB.

View solution in original post

the_wolverine
Champion

Actually, memPoolMB is not related to bucket size, but memory pool allocation.

maxDataSize determines the size of your buckets. On 64-bit architecture, a setting of auto_high_volume will give you a bucket size of 10GB. On 32-bit, this is 750MB.

gkanapathy
Splunk Employee
Splunk Employee

yeah, there's no "tuning" going on. Just "auto".

0 Karma

the_wolverine
Champion

Ok, I didn't realize that there was a separte auto setting. The spec file indicates that "Specifying "auto" or "auto_high_volume" will cause Splunk to autotune this param based on your system (Recommended)"

A value of 100 (or 10GB) does not sound like there's any "auto" tuning going on here.
"

0 Karma

jrodman
Splunk Employee
Splunk Employee

auto for maxDataSize is 100MB for both 64bit and 32bit at this time.

0 Karma

cpenkert
Path Finder

how about just the "auto" setting?

I understand this is different than auto_high.
We are running on 64 bit

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

 Ready to master Kubernetes and cloud monitoring like the pros? Join Splunk’s Growth Engineering team for an ...

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...