Installation

index _internaldb db bigger than configured max of 5gb

mbessel
Engager

Hi,

We are running Splunk v splunk-7.0.0-c8a78efdd40f.x86_64 right now and we have a problem we the internaldb index size. Although we configured a maximum of 5gb it just keeps getting bigger (today we reached 19gb on a 25gb / Partition - dangerous ..) until we restart the Server - then it is instantly flushed and start again at 0. Is this normal? Judging from the default config there is no rotate "time" defined like we did for our application indexes. Should we change that?

Our application indexes are under a 1,5tb /var partition and are constantly being rotated, so this problem really affects only _internaldb size and maybe audit (might be that we had the same problem there in the past)

less ./etc/system/local/indexes.conf

[default]

[_internal]
enableOnlineBucketRepair = 1
enableDataIntegrityControl =
minStreamGroupQueueSize =
streamingTargetTsidxSyncPeriodMsec =
syncMeta = 1
maxTotalDataSizeMB = 5120
journalCompression =
bucketRebuildMemoryHint = 0
compressRawdata = 1
hotBucketTimeRefreshInterval =
maxDataSize = 1024000

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...