<?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 Configuration for heavy forwarder to store events locally when indexer is unavailable? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Configuration-for-heavy-forwarder-to-store-events-locally-when/m-p/330035#M61177</link>
    <description>&lt;P&gt;Dears,&lt;/P&gt;

&lt;P&gt;may i know how to configure splunk Heavy forwarder to store events locally in case of indexer unavailable ?&lt;/P&gt;</description>
    <pubDate>Mon, 30 Oct 2017 22:59:08 GMT</pubDate>
    <dc:creator>ahmedhassanean</dc:creator>
    <dc:date>2017-10-30T22:59:08Z</dc:date>
    <item>
      <title>Configuration for heavy forwarder to store events locally when indexer is unavailable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configuration-for-heavy-forwarder-to-store-events-locally-when/m-p/330035#M61177</link>
      <description>&lt;P&gt;Dears,&lt;/P&gt;

&lt;P&gt;may i know how to configure splunk Heavy forwarder to store events locally in case of indexer unavailable ?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2017 22:59:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configuration-for-heavy-forwarder-to-store-events-locally-when/m-p/330035#M61177</guid>
      <dc:creator>ahmedhassanean</dc:creator>
      <dc:date>2017-10-30T22:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Configuration for heavy forwarder to store events locally when indexer is unavailable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configuration-for-heavy-forwarder-to-store-events-locally-when/m-p/330036#M61178</link>
      <description>&lt;P&gt;Hi ahmedhassanean,&lt;BR /&gt;
if your requirement is to be sure that events will not be lost, you don't need any special configuration: Forwarders (Universal or Heavy) by default locally cache events when Indexers are down.&lt;BR /&gt;
For this reason, if I must ingest syslogs I prefer to use two Heavy Forwarders instead directly receive logs on Indexers.&lt;/P&gt;

&lt;P&gt;If instead your requirement is to access to events in search when an indexer is down, your question isn't  a solution: in this case you have to configure an Indexers cluster.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2017 07:45:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configuration-for-heavy-forwarder-to-store-events-locally-when/m-p/330036#M61178</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-10-31T07:45:14Z</dc:date>
    </item>
  </channel>
</rss>

