Hello.
I explain the scenario:
I have 2 servers destined to different functions ServerA (receive and index, few searches) and ServerB (full searches)
In particular, the ServerB will be the database with /dbsplunk partition with 3TB.
While the ServerA, it will receive the data and index it on the NFS /dbsplunk mounted drive from the ServerB.
So far, the indexing works very well, the data is stored without problems. But when doing searches, both can search the buckets WARM or COLD, but bucket HOT can not be searched. I understand because Splunk blocks the HOT at the time of writing, but I know that Splunk can replicate the HOT files so that other searchers can access the search (1 for each search), according to the following link: http://docs.splunk.com/Documentation/Splunk/6.6.0/Indexer/HowSplunkstoresindexes#Bucket_names
How could I get the ServerA and ServerB to search in bucket HOT at the same time. I know that in the indexes.conf file there is the parameter repFactor = auto, but I do not know how to get it.
Splunk does not handle that situation, as each indexer will try to manage the buckets, and generate conflicts.
Why not use the indexes replication cluster feature to have the indexes you want replicated on the 2 indexers (with replication and search factor 2) ?
will there be someone who has happened to him?