<?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 Delete index foobar info older than 2 weeks. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/13998#M1349</link>
    <description>&lt;P&gt;we only want to save the log info for 2 weeks.  I tried to set this up by modifying the frozen time, but it doesn’t seem to work.  How can I delete info from index foobar database that is older than 2 weeks?&lt;/P&gt;</description>
    <pubDate>Fri, 21 May 2010 20:09:20 GMT</pubDate>
    <dc:creator>dcroteau</dc:creator>
    <dc:date>2010-05-21T20:09:20Z</dc:date>
    <item>
      <title>Delete index foobar info older than 2 weeks.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/13998#M1349</link>
      <description>&lt;P&gt;we only want to save the log info for 2 weeks.  I tried to set this up by modifying the frozen time, but it doesn’t seem to work.  How can I delete info from index foobar database that is older than 2 weeks?&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2010 20:09:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/13998#M1349</guid>
      <dc:creator>dcroteau</dc:creator>
      <dc:date>2010-05-21T20:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Delete index foobar info older than 2 weeks.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/13999#M1350</link>
      <description>&lt;P&gt;Can you post your current index settings for the index in question.  (You can run &lt;CODE&gt;btool indexes layer &amp;lt;your_index_name&amp;gt;&lt;/CODE&gt; to show all the settings applied to your index.)&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2010 20:18:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/13999#M1350</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-05-21T20:18:43Z</dc:date>
    </item>
    <item>
      <title>Re: Delete index foobar info older than 2 weeks.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/14000#M1351</link>
      <description>&lt;P&gt;Off the top of my head, you will probably need to make sure that your buckets are rotated quite frequently, which can be done by setting a very low maximum hot size or setting a short max time span, or both, I suppose.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;indexes.conf:&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[foobar]

# 2 day max for hot
maxHotSpanSecs=172800

# 200 Mb max for hot
maxDataSize = 200

# Expire data after 2 weeks
frozenTimePeriodInSecs=1209600
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;BTW, you can force a delete of events older than 2 weeks by searching for events more than two weeks old, then piping that search through the &lt;CODE&gt;| delete&lt;/CODE&gt; command.  However, this does not free up any disk space; so I'm guessing this isn't what your looking for.&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2010 20:48:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/14000#M1351</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-05-21T20:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: Delete index foobar info older than 2 weeks.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/14001#M1352</link>
      <description>&lt;P&gt;&lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; does &lt;EM&gt;not&lt;/EM&gt; guarantee deletion after that time. It simply means that data &lt;EM&gt;may&lt;/EM&gt; be deleted after that time. Data older than that &lt;EM&gt;will&lt;/EM&gt; in fact be deleted as long as everything else that it shares an index bucket with is also eligible for deletion. This is because deletion (by which I mean actual deletion not the surgical &lt;CODE&gt;| delete&lt;/CODE&gt; command - that doesn't really "delete" data) is done on a whole-bucket basis, so unless an entire bucket is eligible for deletion, none of the data will be deleted.&lt;/P&gt;</description>
      <pubDate>Sat, 22 May 2010 12:45:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-index-foobar-info-older-than-2-weeks/m-p/14001#M1352</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-05-22T12:45:52Z</dc:date>
    </item>
  </channel>
</rss>

