<?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 clearing buffered events in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/clearing-buffered-events/m-p/46165#M8697</link>
    <description>&lt;P&gt;We have a system where the log rotation confuses splunk and splunk starts attempting to reindex the log.  This happened 3 days ago and we Splunk is still trying to catch up.  How can I clear the "buffer" and just tell splunk to start from this point forward?  I think the throughput is saturated and it is sending as many events it can.  When the problem started, we were getting about 9400 duplicate events per 1 event.  We are now at about 50 to 1.  Any ideas on how to make this stop?&lt;/P&gt;</description>
    <pubDate>Tue, 08 May 2012 19:13:12 GMT</pubDate>
    <dc:creator>mcbradford</dc:creator>
    <dc:date>2012-05-08T19:13:12Z</dc:date>
    <item>
      <title>clearing buffered events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/clearing-buffered-events/m-p/46165#M8697</link>
      <description>&lt;P&gt;We have a system where the log rotation confuses splunk and splunk starts attempting to reindex the log.  This happened 3 days ago and we Splunk is still trying to catch up.  How can I clear the "buffer" and just tell splunk to start from this point forward?  I think the throughput is saturated and it is sending as many events it can.  When the problem started, we were getting about 9400 duplicate events per 1 event.  We are now at about 50 to 1.  Any ideas on how to make this stop?&lt;/P&gt;</description>
      <pubDate>Tue, 08 May 2012 19:13:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/clearing-buffered-events/m-p/46165#M8697</guid>
      <dc:creator>mcbradford</dc:creator>
      <dc:date>2012-05-08T19:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: clearing buffered events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/clearing-buffered-events/m-p/46166#M8698</link>
      <description>&lt;P&gt;There are probably several possible reasons for why this is happening, but it's hard to tell from the limited information. &lt;/P&gt;

&lt;P&gt;Have you tried playing with the &lt;CODE&gt;ignoreOlderThan&lt;/CODE&gt; and &lt;CODE&gt;followTail&lt;/CODE&gt; parameters for &lt;CODE&gt;inputs.conf&lt;/CODE&gt;?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;/Kristian&lt;/P&gt;</description>
      <pubDate>Tue, 08 May 2012 19:26:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/clearing-buffered-events/m-p/46166#M8698</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-05-08T19:26:15Z</dc:date>
    </item>
  </channel>
</rss>

