<?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 2 node cluster master reporting single peer to search head when there are 2 indexers in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271985#M52259</link>
    <description>&lt;P&gt;Have 2 node Indexer cluster with a separate cluster master instance and separate SH instance, however when the SH is configured, it only shows 1 peer in the cluster as per attachment &lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/730i827405AF6872600E/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Why would the cluster master report as 1 peer to the SH when it has 2 peers listed in cluster configuration ?&lt;/P&gt;

&lt;P&gt;Cluster master reports replication and search factor OK. see below&lt;/P&gt;

&lt;P&gt;Replication factor met&lt;BR /&gt;
Search factor met&lt;BR /&gt;
All data is searchable&lt;BR /&gt;
Indexing Ready YES&lt;/P&gt;

&lt;P&gt;indexer1 893F55F8-DC7F-4378-A826-8A027763AE1D default&lt;BR /&gt;
Searchable YES&lt;BR /&gt;
Status Up&lt;BR /&gt;
Bucket Count=6391&lt;/P&gt;

&lt;P&gt;indexer2 90619A93-5668-45CB-AE9B-AE05B1ED43EC default&lt;BR /&gt;
Searchable YES&lt;BR /&gt;
Status Up&lt;BR /&gt;
Bucket Count=107&lt;/P&gt;</description>
    <pubDate>Wed, 14 Oct 2015 02:38:04 GMT</pubDate>
    <dc:creator>sanjeewa_fernan</dc:creator>
    <dc:date>2015-10-14T02:38:04Z</dc:date>
    <item>
      <title>2 node cluster master reporting single peer to search head when there are 2 indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271985#M52259</link>
      <description>&lt;P&gt;Have 2 node Indexer cluster with a separate cluster master instance and separate SH instance, however when the SH is configured, it only shows 1 peer in the cluster as per attachment &lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/730i827405AF6872600E/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Why would the cluster master report as 1 peer to the SH when it has 2 peers listed in cluster configuration ?&lt;/P&gt;

&lt;P&gt;Cluster master reports replication and search factor OK. see below&lt;/P&gt;

&lt;P&gt;Replication factor met&lt;BR /&gt;
Search factor met&lt;BR /&gt;
All data is searchable&lt;BR /&gt;
Indexing Ready YES&lt;/P&gt;

&lt;P&gt;indexer1 893F55F8-DC7F-4378-A826-8A027763AE1D default&lt;BR /&gt;
Searchable YES&lt;BR /&gt;
Status Up&lt;BR /&gt;
Bucket Count=6391&lt;/P&gt;

&lt;P&gt;indexer2 90619A93-5668-45CB-AE9B-AE05B1ED43EC default&lt;BR /&gt;
Searchable YES&lt;BR /&gt;
Status Up&lt;BR /&gt;
Bucket Count=107&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2015 02:38:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271985#M52259</guid>
      <dc:creator>sanjeewa_fernan</dc:creator>
      <dc:date>2015-10-14T02:38:04Z</dc:date>
    </item>
    <item>
      <title>Re: 2 node cluster master reporting single peer to search head when there are 2 indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271986#M52260</link>
      <description>&lt;P&gt;Hi @sanjeewa_fernando, &lt;/P&gt;

&lt;P&gt;just to let you know, that I deleted the duplicate question from the moderation queue.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2015 03:00:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271986#M52260</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-10-14T03:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: 2 node cluster master reporting single peer to search head when there are 2 indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271987#M52261</link>
      <description>&lt;P&gt;Where is your Search Head pointing? To the CM or to the Indexer? In a clustered configuration, your search heads should all point to the Cluster Master. The cluster master will then distribute the list of indexers for search.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2015 04:46:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271987#M52261</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2015-10-14T04:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: 2 node cluster master reporting single peer to search head when there are 2 indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271988#M52262</link>
      <description>&lt;P&gt;Hi, found out there was an issue with the Firewall rule connecting the Clustered SH, when the FW rule was opened (8080/8089) it worked &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 22:17:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-node-cluster-master-reporting-single-peer-to-search-head-when/m-p/271988#M52262</guid>
      <dc:creator>sanjeewa_fernan</dc:creator>
      <dc:date>2015-10-22T22:17:29Z</dc:date>
    </item>
  </channel>
</rss>

