I thought that there would be 1024 MBs in 1 GB, but the examples online for indexes.conf has these entries:
### Indexes may be allocated space in effective groups by sharing volumes ###
# perhaps we only want to keep 100GB of summary data and other
# low-volume information
[volume:small_indexes]
path = /mnt/splunk_indexes
maxVolumeDataSizeMB = 100000
# and this is our main event series, allowing 50 terabytes
[volume:large_indexes]
path = /mnt/splunk_indexes
maxVolumeDataSizeMB = 50000000
Shouldn't 50 terabyes be defined as 52428800? I am tuning my indexes.conf config and want to be as precice as possible.
Thank you,
Jim
Well, according to my license key, Splunk represents 1 GB = 1024 MB, so I would use that as a benchmark.
In that case, it could just be a representation error in the comment field which resulted in the confusion. I would still continue to use 1024 as the base instead of 1000 in my configurations.
I also verified these answers with support.
To concur with twkan , I've just looked 3 different license files of different volumes and :
Perhaps the author of the example made an oversight in the comments.
Well, according to my license key, Splunk represents 1 GB = 1024 MB, so I would use that as a benchmark.
In that case, it could just be a representation error in the comment field which resulted in the confusion. I would still continue to use 1024 as the base instead of 1000 in my configurations.