The important part (and missing from your post) is how much of that allocated space is actually "in-use"? If you are using all 8TB of hot and 160TB of cold, then there is no way around it - you need more disk. However, if your true usage of space falls below this, then you can set your limits to match the space that is available. For example. if your only using 4TB of your 8TB actual hot-device you can safely amend the maxVolumeDataSizeMB to 1TB on each host. You should also understand that if you set the maxVol.. to a value smaller than what you have in current use will only cause that data to roll to cold - not be removed. The limits only tell Splunk what to do at those limits, so as long as you have a small amount of Cold space you can add your new indexers leaving the cold maxVol... set to 40TB each (320 total) Let the cluster replicate and balance, then when that process is complete you can reduce it to 20TB each. But, Ideally your retention should be dictated by dates rather than volume. I tend to think of the maxVol.. setting as a safety net incase you are getting close to the physical limits of the hardware, but what really drives my storage is how long i need to keep that data for.
... View more