<?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 Re: Single Site or Multi Site Indexer Clustering in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531042#M18272</link>
    <description>&lt;P&gt;Yes, you'll likely want a replication factor of 2.&lt;/P&gt;&lt;P&gt;400GB per day is a little high for 2 indexers, but may be tough for a single indexer to handle should one of them fail.&amp;nbsp; A lot depends on the complexity of work being done on the data as well as how many searches it's processing.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Nov 2020 17:39:56 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-11-26T17:39:56Z</dc:date>
    <item>
      <title>Single Site or Multi Site Indexer Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/530992#M18268</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;&lt;P&gt;We have servers running on 2 different on premises Data Centre.&lt;/P&gt;&lt;P&gt;We are planning Splunk deployment architecture to fetch the events from server.&lt;/P&gt;&lt;P&gt;We are planning to have 1 indexer at each Data Centre and making a clustering of this 2 indexers.&lt;/P&gt;&lt;P&gt;Reason for clustering is suppose 1 indexer goes down then the other one can keep on fetching events from the servers of other DC with no downtime with these aspects.&lt;/P&gt;&lt;P&gt;And clustering will also help us to use 1 search head for both DCs as we dont have many users for monitoring.&lt;/P&gt;&lt;P&gt;Both Data centres are connected to each other with some dedicated LAN channels....&lt;/P&gt;&lt;P&gt;Both indexers would be under same virtual network.&lt;/P&gt;&lt;P&gt;Will this be as simple as single site cluster??? If I configure them as single site cluster would there be any architectural issues or I'm going in right way?&lt;/P&gt;&lt;P&gt;Or will their be a concept multi site needs to be implemented?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2020 11:00:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/530992#M18268</guid>
      <dc:creator>hectorvp</dc:creator>
      <dc:date>2020-11-26T11:00:15Z</dc:date>
    </item>
    <item>
      <title>Re: Single Site or Multi Site Indexer Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531031#M18269</link>
      <description>&lt;P&gt;First, clustering is not necessary for a single SH to search multiple indexers.&lt;/P&gt;&lt;P&gt;When sizing your 2 indexers, make each capable of handling 100% of the ingestion and search load.&amp;nbsp; There's no point in having redundancy if the backup fails under the full load.&lt;/P&gt;&lt;P&gt;Go with a multi-site cluster, even if you decide to treat both DCs as a single site.&amp;nbsp; The multi-site configuration will make it easier to switch to a true multi-site operation later.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2020 16:06:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531031#M18269</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-11-26T16:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: Single Site or Multi Site Indexer Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531034#M18270</link>
      <description>&lt;P&gt;Thanks &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;So we would opt for multi site configuration.&lt;/P&gt;&lt;P&gt;Where 1 DC will contain 1 indexer and master node and other DC will contain another 1 indexer.&lt;/P&gt;&lt;P&gt;Well when each indexer should be capable of 100% ingestion means we need to size its disk space to capable of storing all events.Along with other specs recommended by Splunk.&lt;/P&gt;&lt;P&gt;And having replication factor to 2, did I understood this in a right way?&lt;/P&gt;&lt;P&gt;Currently we have estimated that total events generated by DCs would be around 400GB per day.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2020 16:35:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531034#M18270</guid>
      <dc:creator>hectorvp</dc:creator>
      <dc:date>2020-11-26T16:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: Single Site or Multi Site Indexer Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531042#M18272</link>
      <description>&lt;P&gt;Yes, you'll likely want a replication factor of 2.&lt;/P&gt;&lt;P&gt;400GB per day is a little high for 2 indexers, but may be tough for a single indexer to handle should one of them fail.&amp;nbsp; A lot depends on the complexity of work being done on the data as well as how many searches it's processing.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2020 17:39:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531042#M18272</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-11-26T17:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: Single Site or Multi Site Indexer Clustering</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531043#M18273</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, these are other complexities as well as we are going to route these events to other third party indexers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2020 17:51:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Site-or-Multi-Site-Indexer-Clustering/m-p/531043#M18273</guid>
      <dc:creator>hectorvp</dc:creator>
      <dc:date>2020-11-26T17:51:31Z</dc:date>
    </item>
  </channel>
</rss>

