Getting Data In

Setting up indexes.conf

ips_mandar
Builder

Hi,
I am setting indexes.conf file where I am going to fix homepath and coldpah sizes. for ex.-

[myindex]
 homePath = FASTDISK:\splunk\myindex\db
 coldPath = SLOWDISK:\splunk\myindex\colddb
 thawedPath = SLOWDISK:\splunk\myindex\thaweddb
 coldToFrozenDir = ARCHIVEDISK:\splunk\myindex\frozen
 **maxTotalDataSizeMB = 1000000**
homePath.maxDataSizeMB = 600000
coldPath.maxDataSizeMB = 400000
 frozenTimePeriodInSecs = 31536000

Here I have below questions-
1. If I am setting separately homepath and coldpath sizes then why it is required to mention whole index size as well i.e. maxTotalDataSizeMB or it is not mandatory?
2. I read somewhere that for thawedPath does not take into consideration any environment variable/volume path referenced. is it correct? then I have to manually set thawedPath.

Thanks,

0 Karma

bangalorep
Communicator

Hi,

You have to specify maxTotalDataSizeMB as this parameter dictates the freezing of your data.
thawedPath cannot contain a volume reference. It says so in the documentation as well. https://docs.splunk.com/Documentation/Splunk/8.0.1/Admin/Indexesconf

0 Karma

ips_mandar
Builder

Thanks @bangalorep.
Can you please explain me why maxTotalDataSizeMB is required because even coldPath.maxDataSizeMB dictates freezing of data once coldpath size exceeded.

0 Karma
Get Updates on the Splunk Community!

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...

Cloud Platform & Enterprise: Classic Dashboard Export Feature Deprecation

As of Splunk Cloud Platform 9.3.2408 and Splunk Enterprise 9.4, classic dashboard export features are now ...