<?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: If a peer goes down in an indexer cluster, how does new indexed data get replicated, and what happens when the peer comes back up later? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/If-a-peer-goes-down-in-an-indexer-cluster-how-does-new-indexed/m-p/281074#M10662</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;For replication factor 3 you need 3 peers, in this case if your peers goes down the replication factor is not meet until you add other indexer, but your search factor will be  meet after the fix process.&lt;/P&gt;

&lt;P&gt;When your down peer goes up the master will rebuild the cluster make all the copies needed and yes after the rebuild all your peers will have a copy of the indexed data doesn't matter the time was down the indexer.&lt;/P&gt;

&lt;P&gt;Hope i help you&lt;/P&gt;</description>
    <pubDate>Mon, 06 Jun 2016 15:32:51 GMT</pubDate>
    <dc:creator>jmallorquin</dc:creator>
    <dc:date>2016-06-06T15:32:51Z</dc:date>
    <item>
      <title>If a peer goes down in an indexer cluster, how does new indexed data get replicated, and what happens when the peer comes back up later?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/If-a-peer-goes-down-in-an-indexer-cluster-how-does-new-indexed/m-p/281073#M10661</link>
      <description>&lt;P&gt;Little confused in Indexer Clustering. I have 3 peers with One master and One Search Head. Replication Factor is 3 and Search Factor is 2. If one of the indexers goes down, Master can manage with 2 searchable copies by moving the primacy and convert non-searchable into searchable. Search Factor is good, but in this case, my rep factor is 3 and number of peers also 3. If one of the peers goes down, RF could not be met and this cluster is valid, but incomplete. Two questions here:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;If new data comes, how does it get replicated? Is it going to store only two copies of data in available indexers (one original + one replicated)?&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;What happen if my downed peer came back after one week? Whether the new data captured during last week is going to get copied in this peer?&lt;/P&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 08:50:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/If-a-peer-goes-down-in-an-indexer-cluster-how-does-new-indexed/m-p/281073#M10661</guid>
      <dc:creator>splunkn</dc:creator>
      <dc:date>2016-06-06T08:50:41Z</dc:date>
    </item>
    <item>
      <title>Re: If a peer goes down in an indexer cluster, how does new indexed data get replicated, and what happens when the peer comes back up later?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/If-a-peer-goes-down-in-an-indexer-cluster-how-does-new-indexed/m-p/281074#M10662</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;For replication factor 3 you need 3 peers, in this case if your peers goes down the replication factor is not meet until you add other indexer, but your search factor will be  meet after the fix process.&lt;/P&gt;

&lt;P&gt;When your down peer goes up the master will rebuild the cluster make all the copies needed and yes after the rebuild all your peers will have a copy of the indexed data doesn't matter the time was down the indexer.&lt;/P&gt;

&lt;P&gt;Hope i help you&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 15:32:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/If-a-peer-goes-down-in-an-indexer-cluster-how-does-new-indexed/m-p/281074#M10662</guid>
      <dc:creator>jmallorquin</dc:creator>
      <dc:date>2016-06-06T15:32:51Z</dc:date>
    </item>
  </channel>
</rss>

