Assume I have a cluster of three indexers. They each have an array of SSDs and an array of SAS disks. The cluster would be configured for single redundancy of data. I would want to configure the hot/warm location of my critical indexes to run on the SSDs.
When the cluster members replicate data from buckets on the SSDs, is there any way to control where the redundant copy of the data goes? Can I store my redundant data on the slower, cheaper disks?
Thanks.
Craig
In Splunk 5.0, the replicated copies always live in the colddb path. So if you configure your Cold path on slower disks, then you will get the behavior you are looking for.
In Splunk 5.0, the replicated copies always live in the colddb path. So if you configure your Cold path on slower disks, then you will get the behavior you are looking for.