<?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: Replication Factor for different buckets in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555969#M6126</link>
    <description>&lt;P&gt;You're correct&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/106850"&gt;@gjanders&lt;/a&gt;&amp;nbsp;, the empty directories got me. Thank you for your help. Those looking for the doc:&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/IndexerclusteroperationsandSmartStore" target="_self"&gt;&amp;nbsp;https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/IndexerclusteroperationsandSmartStore&lt;/A&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;P&gt;For example, if the cluster has a replication factor of 3, three peer nodes continue to maintain metadata information, along with populated or empty directories, for each bucket.&lt;/P&gt;&lt;P&gt;By maintaining metadata for each bucket on the replication factor number of peer nodes, the cluster simplifies the process of fetching the bucket when it is needed, in the case of any interim peer node failure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Wed, 16 Jun 2021 13:02:11 GMT</pubDate>
    <dc:creator>wgawhh5hbnht</dc:creator>
    <dc:date>2021-06-16T13:02:11Z</dc:date>
    <item>
      <title>Replication Factor for different buckets</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555687#M6115</link>
      <description>&lt;P&gt;There isn't a way to set RF for different buckets, right? e.g. hot RF 2, cold no RF&lt;/P&gt;&lt;P&gt;We're using smartstore, therefor S3 is handling cold bucket replication and it would drastically reduce the storage cost if we could only have RF for hot buckets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've see &lt;A href="https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-in-an-indexer-cluster-to-apply-a-different/m-p/247687#M9344" target="_self"&gt;this post&lt;/A&gt;, but it's been a few years.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jun 2021 19:06:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555687#M6115</guid>
      <dc:creator>wgawhh5hbnht</dc:creator>
      <dc:date>2021-06-14T19:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: Replication Factor for different buckets</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555910#M6124</link>
      <description>&lt;P&gt;The search replication factor and replication factor only relate to hot buckets when using smartstore. Only 1 copy of a bucket is uploaded to the object storage&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jun 2021 05:11:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555910#M6124</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2021-06-16T05:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Replication Factor for different buckets</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555969#M6126</link>
      <description>&lt;P&gt;You're correct&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/106850"&gt;@gjanders&lt;/a&gt;&amp;nbsp;, the empty directories got me. Thank you for your help. Those looking for the doc:&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/IndexerclusteroperationsandSmartStore" target="_self"&gt;&amp;nbsp;https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/IndexerclusteroperationsandSmartStore&lt;/A&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;P&gt;For example, if the cluster has a replication factor of 3, three peer nodes continue to maintain metadata information, along with populated or empty directories, for each bucket.&lt;/P&gt;&lt;P&gt;By maintaining metadata for each bucket on the replication factor number of peer nodes, the cluster simplifies the process of fetching the bucket when it is needed, in the case of any interim peer node failure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Wed, 16 Jun 2021 13:02:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Replication-Factor-for-different-buckets/m-p/555969#M6126</guid>
      <dc:creator>wgawhh5hbnht</dc:creator>
      <dc:date>2021-06-16T13:02:11Z</dc:date>
    </item>
  </channel>
</rss>

