<?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: Smartstore configuration multisite cluster in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535664#M4873</link>
    <description>&lt;P&gt;Hi, Thx for the response. I am talking about a multisite cluster stretched two regions. This is a single cluster across two regions.&lt;/P&gt;</description>
    <pubDate>Wed, 13 Jan 2021 14:10:22 GMT</pubDate>
    <dc:creator>raviadapa</dc:creator>
    <dc:date>2021-01-13T14:10:22Z</dc:date>
    <item>
      <title>Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535646#M4871</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am working on a project for a client to implement Splunk as a primary logging platform. I have designed the solution to use a multisite cluster across two aws regions. I am struggling to get how i can deploy smartstore in the two regions, which basically will have ind in region A connect to smartstore and ind in region B conn to smartstore in region B. Can you provide an example of this type of configuration.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 12:59:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535646#M4871</guid>
      <dc:creator>raviadapa</dc:creator>
      <dc:date>2021-01-13T12:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535662#M4872</link>
      <description>&lt;P&gt;It sounds like you want the indexer clusters to share a SmartStore.&amp;nbsp; Don't.&amp;nbsp; Each cluster should have it's own, separate S2 .&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 14:08:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535662#M4872</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-13T14:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535664#M4873</link>
      <description>&lt;P&gt;Hi, Thx for the response. I am talking about a multisite cluster stretched two regions. This is a single cluster across two regions.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 14:10:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535664#M4873</guid>
      <dc:creator>raviadapa</dc:creator>
      <dc:date>2021-01-13T14:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535671#M4874</link>
      <description>&lt;P&gt;Thanks for clarifying.&amp;nbsp; See&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Archive/is-multi-site-cluster-architecture-the-same-as-multi-region/m-p/429014" target="_blank"&gt;https://community.splunk.com/t5/Archive/is-multi-site-cluster-architecture-the-same-as-multi-region/m-p/429014 &lt;/A&gt;and&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Knowledge-Management/Smartstore-How-to-deal-with-Multi-site-when-sites-are-in/m-p/496603" target="_blank"&gt;https://community.splunk.com/t5/Knowledge-Management/Smartstore-How-to-deal-with-Multi-site-when-sites-are-in/m-p/496603&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 14:52:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535671#M4874</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-13T14:52:07Z</dc:date>
    </item>
    <item>
      <title>Re: Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535672#M4875</link>
      <description>&lt;P&gt;Hi Richgalloway,&lt;/P&gt;&lt;P&gt;Thx for the reply. I will read see the recommended solutions below.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 14:58:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/535672#M4875</guid>
      <dc:creator>raviadapa</dc:creator>
      <dc:date>2021-01-13T14:58:54Z</dc:date>
    </item>
    <item>
      <title>Re: Smartstore configuration multisite cluster</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/612170#M9002</link>
      <description>&lt;P&gt;Isn't it what a multi-site smartstore should have, a single smartstore shared by the indexers from two sites that are part of the same cluster?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also if they are part of the same cluster, wouldn't Cluster Manager push the indexes.conf across all sites which means, the remote volume details has to be the same across the indexers on each site (like the endpoint, bucket name, credentials)?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 22:15:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Smartstore-configuration-multisite-cluster/m-p/612170#M9002</guid>
      <dc:creator>srajarat2</dc:creator>
      <dc:date>2022-09-06T22:15:56Z</dc:date>
    </item>
  </channel>
</rss>

