<?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: Indexer Replication Failover Testing in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-Replication-Failover-Testing/m-p/110955#M4206</link>
    <description>&lt;P&gt;R.Turk,&lt;/P&gt;

&lt;P&gt;How much data did you index? (The replication is not per-event but per some amount of data. I'm wondering if the replication never happened before the shutdown.) &lt;/P&gt;

&lt;P&gt;Also are you sending data via forwarder or local file via monitors? If forwarders, is your forwarder auto-lbing across all the peers? If the peer goes down without replicating the data, then the forwarder should just send the data to some other peer. &lt;/P&gt;

&lt;P&gt;But if you are indexing local files via monitors that won't happen. You should be using forwarders that have acks turned on and set to auto-lb across all those peers.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Nov 2013 22:44:06 GMT</pubDate>
    <dc:creator>svasan_splunk</dc:creator>
    <dc:date>2013-11-11T22:44:06Z</dc:date>
    <item>
      <title>Indexer Replication Failover Testing</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-Replication-Failover-Testing/m-p/110954#M4205</link>
      <description>&lt;P&gt;Hello Splunkers!&lt;/P&gt;

&lt;P&gt;I have two clustered indexers (v5.0.4) replicating buckets between them. I have been testing the failover mechanism to tick a box saying that the data is indeed searchable if an indexer fails. The testing methodology is as follows:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Run a search (e.g. &lt;CODE&gt;index=main&lt;/CODE&gt;) for a window of time in the past.&lt;/LI&gt;
&lt;LI&gt;Confirm the number of results returned from each &lt;CODE&gt;splunk_server&lt;/CODE&gt;, and the total number of events returned&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;offline&lt;/CODE&gt; one of the indexers (IDX-A)&lt;/LI&gt;
&lt;LI&gt;Re-run the test for the same period of time to confirm identical results are returned.&lt;/LI&gt;
&lt;LI&gt;???&lt;/LI&gt;
&lt;LI&gt;PROFIT!!&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;All pretty simple right? (apart from 5 &amp;amp; 6 anyway). &lt;/P&gt;

&lt;P&gt;The problem I have is with step 4 - I do &lt;STRONG&gt;not&lt;/STRONG&gt; get the results that were previously returned from the now offline indexer IDX-A. I have waited for ~10 minutes with no joy. I have a rep factor &amp;amp; search factor of 2, and the cluster master reports that everything is hunky-dory. But as soon as I restart the splunkd process on IDX-A, I get the correct/expected number of results from IDX-B. So yes, replication works... but I'd have expected the resumption of service on IDX-A not to be a trigger/catalyst for IDX-B actually returning events previously held by IDX-A.&lt;/P&gt;

&lt;P&gt;Is there a setting/timer I'm missing here? Happy to be pointed in the right direction!&lt;/P&gt;

&lt;P&gt;Thanks in advance &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;RT&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2013 06:48:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Indexer-Replication-Failover-Testing/m-p/110954#M4205</guid>
      <dc:creator>rturk</dc:creator>
      <dc:date>2013-10-23T06:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Replication Failover Testing</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-Replication-Failover-Testing/m-p/110955#M4206</link>
      <description>&lt;P&gt;R.Turk,&lt;/P&gt;

&lt;P&gt;How much data did you index? (The replication is not per-event but per some amount of data. I'm wondering if the replication never happened before the shutdown.) &lt;/P&gt;

&lt;P&gt;Also are you sending data via forwarder or local file via monitors? If forwarders, is your forwarder auto-lbing across all the peers? If the peer goes down without replicating the data, then the forwarder should just send the data to some other peer. &lt;/P&gt;

&lt;P&gt;But if you are indexing local files via monitors that won't happen. You should be using forwarders that have acks turned on and set to auto-lb across all those peers.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2013 22:44:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Indexer-Replication-Failover-Testing/m-p/110955#M4206</guid>
      <dc:creator>svasan_splunk</dc:creator>
      <dc:date>2013-11-11T22:44:06Z</dc:date>
    </item>
  </channel>
</rss>

