Monitoring Splunk

Storage issues on indexer

Reethika
Path Finder

 

Is it normal to have colddb > db?


4.0K    thaweddb
20M     summary
4.2G    datamodel_summary
9.8G    db
59G     colddb
[root@xxxxxxxplunkdata/_internaldb

Labels (2)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @Reethika ,

it depends on the parameters you configured in your Splunk installation,

as you can see in https://docs.splunk.com/Documentation/Splunk/latest/Admin/Indexesconf there are many parameters to configure how long a bucket remains in Warm Data (db) and how long it remains in Cold Data (colddb).

at first, what's the retention of your archive? if you have a long retention (frozenTimePriodInSeconds), buckets stay most time in Cold State.

if you leave the the number of warm as default and you have many data, the pass quickly from Warm to Cold (default of maxWarmDbCount is 300).

In other words it's normal, unless you setted a different configuration.

Ciao.

Giuseppe

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

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

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...