<?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 Indexer goes down, Stop the Splunk-forwarder from sending in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43065#M8032</link>
    <description>&lt;P&gt;I have been doing some research into what to my Splunk Forwarder can happen if my Splunk indexer goes down, I have noticed that it may will continue to queue the data in memory until full, this isn't what I had in mind as it will fill up what I can send through the bandwidth connection between the forwarder and the indexer.&lt;/P&gt;

&lt;P&gt;I have noticed that there is a &lt;STRONG&gt;useACK=true&lt;/STRONG&gt; in outputs.conf on the forwarder side, ifset to true I can then set both &lt;STRONG&gt;readTimeout&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;writeTimeot&lt;/STRONG&gt; parameters to stop when the is no acknowledgement from the Splunk indexer, I have no idea if indeed setting the acknowledgement functionality also includes me setting up how much i want to indexer to index before sending in another patch for indexing, does this have to be specified manually?, is the &lt;STRONG&gt;useACK=true&lt;/STRONG&gt; the best option I have?&lt;/P&gt;

&lt;P&gt;As I would rather have the Splunk Forwarder stop sending through anything once the Splunk indexer indeed goes down.&lt;/P&gt;</description>
    <pubDate>Mon, 25 Feb 2013 22:29:23 GMT</pubDate>
    <dc:creator>Dark_Ichigo</dc:creator>
    <dc:date>2013-02-25T22:29:23Z</dc:date>
    <item>
      <title>Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43065#M8032</link>
      <description>&lt;P&gt;I have been doing some research into what to my Splunk Forwarder can happen if my Splunk indexer goes down, I have noticed that it may will continue to queue the data in memory until full, this isn't what I had in mind as it will fill up what I can send through the bandwidth connection between the forwarder and the indexer.&lt;/P&gt;

&lt;P&gt;I have noticed that there is a &lt;STRONG&gt;useACK=true&lt;/STRONG&gt; in outputs.conf on the forwarder side, ifset to true I can then set both &lt;STRONG&gt;readTimeout&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;writeTimeot&lt;/STRONG&gt; parameters to stop when the is no acknowledgement from the Splunk indexer, I have no idea if indeed setting the acknowledgement functionality also includes me setting up how much i want to indexer to index before sending in another patch for indexing, does this have to be specified manually?, is the &lt;STRONG&gt;useACK=true&lt;/STRONG&gt; the best option I have?&lt;/P&gt;

&lt;P&gt;As I would rather have the Splunk Forwarder stop sending through anything once the Splunk indexer indeed goes down.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2013 22:29:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43065#M8032</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2013-02-25T22:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43066#M8033</link>
      <description>&lt;P&gt;This is already the default behavior:&lt;BR /&gt;
if the indexer refuses data (full or down) then the forwarders fill their memory queue up to 2MB (default), then pause the monitoring.&lt;/P&gt;

&lt;P&gt;Using useACK will only be useful if you have an unreliable connection and want the indexers to send an acknowledgment to the forwarders who otherwise will resent the events.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2013 23:15:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43066#M8033</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2013-02-25T23:15:49Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43067#M8034</link>
      <description>&lt;P&gt;Is there a way to modify the max queue in the case to higher or lower than the default 2MB to stop it from forwarding data?&lt;/P&gt;

&lt;P&gt;Does it keep logging events in the logs after it stops as well, repeatedly that its failing to send?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2013 23:20:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43067#M8034</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2013-02-25T23:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43068#M8035</link>
      <description>&lt;P&gt;In outputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
maxQueueSize = 1MB
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 26 Feb 2013 09:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43068#M8035</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-02-26T09:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43069#M8036</link>
      <description>&lt;P&gt;Thanks, but I take it we need to set &lt;STRONG&gt;useACK=true&lt;/STRONG&gt; first?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2013 22:41:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43069#M8036</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2013-02-26T22:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer goes down, Stop the Splunk-forwarder from sending</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43070#M8037</link>
      <description>&lt;P&gt;I don't think so.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/admin/outputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/admin/outputsconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2013 07:34:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-goes-down-Stop-the-Splunk-forwarder-from-sending/m-p/43070#M8037</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-02-27T07:34:56Z</dc:date>
    </item>
  </channel>
</rss>

