<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Splunk Index Clustering in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371344#M13638</link>
    <description>&lt;P&gt;We have a multi-site cluster of 6.6.4 (site1, site2) and when testing a downed state of site1, some of our forwarders were not failing to the site that was up. Or, we saw odd behavior like forwarders still attempting to hit site1 AND site2 (almost like a round robin) indexers despite the cluster master noting them as unknown/down. &lt;/P&gt;

&lt;P&gt;Here is what our outputs.conf looks like:&lt;/P&gt;

&lt;P&gt;[tcpout]&lt;BR /&gt;
defaultGroup = primary_indexers&lt;BR /&gt;
maxQueueSize = 7MB&lt;BR /&gt;
useACK = true&lt;BR /&gt;
forceTimebasedAutoLB = true&lt;BR /&gt;
forwardedindex.2.whitelist = (_audit|_introspection|_internal)&lt;/P&gt;

&lt;P&gt;[tcpout:primary_indexers]&lt;BR /&gt;
indexerDiscovery = clustered_indexers&lt;/P&gt;

&lt;P&gt;sslCertPath = $SPLUNK_HOME/etc/apps/forwarderoutputs/local/splunkforwarder.pem&lt;BR /&gt;
sslPassword = pass&lt;BR /&gt;
sslVerifyServerCert = true&lt;/P&gt;

&lt;P&gt;[indexer_discovery:clustered_indexers]&lt;BR /&gt;
pass4SymmKey = pass&lt;BR /&gt;
master_uri = &lt;A href="https://clustermaster:8089" target="_blank"&gt;https://clustermaster:8089&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;[tcpout-server://site01index01:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site01index01, site01index01.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site01index02:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site01index02, site01index02.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site2index01:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site02index01, site02index01.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site2index02:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site02index02, site02index02.domain.com&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 19:18:58 GMT</pubDate>
    <dc:creator>Kendo213</dc:creator>
    <dc:date>2020-09-29T19:18:58Z</dc:date>
    <item>
      <title>Splunk Index Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371344#M13638</link>
      <description>&lt;P&gt;We have a multi-site cluster of 6.6.4 (site1, site2) and when testing a downed state of site1, some of our forwarders were not failing to the site that was up. Or, we saw odd behavior like forwarders still attempting to hit site1 AND site2 (almost like a round robin) indexers despite the cluster master noting them as unknown/down. &lt;/P&gt;

&lt;P&gt;Here is what our outputs.conf looks like:&lt;/P&gt;

&lt;P&gt;[tcpout]&lt;BR /&gt;
defaultGroup = primary_indexers&lt;BR /&gt;
maxQueueSize = 7MB&lt;BR /&gt;
useACK = true&lt;BR /&gt;
forceTimebasedAutoLB = true&lt;BR /&gt;
forwardedindex.2.whitelist = (_audit|_introspection|_internal)&lt;/P&gt;

&lt;P&gt;[tcpout:primary_indexers]&lt;BR /&gt;
indexerDiscovery = clustered_indexers&lt;/P&gt;

&lt;P&gt;sslCertPath = $SPLUNK_HOME/etc/apps/forwarderoutputs/local/splunkforwarder.pem&lt;BR /&gt;
sslPassword = pass&lt;BR /&gt;
sslVerifyServerCert = true&lt;/P&gt;

&lt;P&gt;[indexer_discovery:clustered_indexers]&lt;BR /&gt;
pass4SymmKey = pass&lt;BR /&gt;
master_uri = &lt;A href="https://clustermaster:8089" target="_blank"&gt;https://clustermaster:8089&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;[tcpout-server://site01index01:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site01index01, site01index01.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site01index02:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site01index02, site01index02.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site2index01:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site02index01, site02index01.domain.com&lt;/P&gt;

&lt;P&gt;[tcpout-server://site2index02:9998]&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslAltNameToCheck = site02index02, site02index02.domain.com&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 19:18:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371344#M13638</guid>
      <dc:creator>Kendo213</dc:creator>
      <dc:date>2020-09-29T19:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Index Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371345#M13639</link>
      <description>&lt;P&gt;Can you state your question more clearly please ? &lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 15:03:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371345#M13639</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2018-04-30T15:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Index Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371346#M13640</link>
      <description>&lt;P&gt;I guess I would expect my forwarders to hit the cluster master, and be told that "these indexers are down" and start forwarding to the indexers that are up according to the cluster master.  That doesn't seem to be happening&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 15:09:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371346#M13640</guid>
      <dc:creator>Kendo213</dc:creator>
      <dc:date>2018-04-30T15:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Index Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371347#M13641</link>
      <description>&lt;P&gt;Isn't that a result of specifying those tcpout-server stanzas? As far as I understand, those are not necessary when using indexer discovery. Why do you have those?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 15:32:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371347#M13641</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2018-04-30T15:32:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Index Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371348#M13642</link>
      <description>&lt;P&gt;That's what I was thinking, however this is how Splunk PS configured it.  &lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 15:41:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Index-Clustering/m-p/371348#M13642</guid>
      <dc:creator>Kendo213</dc:creator>
      <dc:date>2018-04-30T15:41:47Z</dc:date>
    </item>
  </channel>
</rss>

