Splunk Search

hot_v* file not found but able to see file using locate

wuming79
Path Finder

Hi,

Referencing to http://docs.splunk.com/Documentation/Splunk/6.2.1/Capacity/Estimateyourstoragerequirements,
I'm trying to estimate my storage space on Linux. At /opt/splunk/var/lib/splunk/defaultdb, when I run "du -ch hot_v*", terminal says no such file or directory.

I did a locate hot_v and a list below came up and one of them in the db folder is hot_v1_12.
I then did a ls -a and I can't find hot_v1_12.

Anyone encounter this issue before?

alt text

Tags (1)
0 Karma

s2_splunk
Splunk Employee
Splunk Employee

The digits at the end of the hot bucket directories are sequential numbers. Hot buckets are rolled to warm (db_*) based on index configuration parameters, or when you stop/restart splunk. So those hot bucket names change all the time as new data comes in.
defaultdb is (by default) mapped to the 'main' index. If you don't ingest any data here, you won't have hot buckets.
I would recommend you use the Splunk Sizing Tool to figure out what your storage requirements are.
Select your daily data volume, retention settings, etc. and it will give you an estimate on per-indexer and total data storage needs for HOT/WARM and COLD volumes.

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 ...