Hi All. I was thinking about the configuration af an Index Cluster Deployer (formerly known as Master), where best practises are, that it should forward data to the index tier, this makes absolutely sense. But why not use it self to define the peers, the same way all other forwarders use it. So I get an outputs.conf with this content: [indexer_discovery:master1]
pass4SymmKey = *****
master_uri = https://127.0.0.1:8089
[tcpout:prod]
indexerDiscovery = master1
useACK = true
[tcpout]
defaultGroup = prod I tried it on a 8.1.0 just released instanse on Splunk Enterprise, but it seems I get some sort of race condition, where the Cluster Master isn't available when the TCP-out process need to uild the indexer list. Has anybody else seen this, found a workaround or is this by design? Kind regards and happy .conf las
... View more