<?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: bucket retention and frozenTimePeriodInSecs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116366#M24282</link>
    <description>&lt;P&gt;A bucket that contains events overlapping the time retention will not be frozen until all the events are older than the retention.&lt;/P&gt;

&lt;P&gt;By default indexes.conf has buckets with up to 3 months of span. So It's possible that you have buckets still overlapping&lt;BR /&gt;
&lt;CODE&gt;[main]&lt;BR /&gt;
maxHotSpanSecs = 7776000&lt;BR /&gt;
frozenTimePeriodInSecs = 188697600&lt;BR /&gt;
&lt;/CODE&gt;&lt;BR /&gt;
A workaround may be to reduce the maxHotSpanSecs to a week, to force the buckets to be smaller, and rotate more often.&lt;/P&gt;

&lt;P&gt;To verify the status of your buckets, and estimate if they meet the condition to be frozen you can use those dbinspect searches on the indexer.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt; for Splunk 6, for all indexes with autodetection from frozenTimePeriodInSecs &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;CODE&gt;| dbinspect index=* | join index [|rest /services/data/indexes| eval index=title | table index frozenTimePeriodInSecs ] &lt;BR /&gt;
| eval toNow=now()-endEpoch | convert num(toNow) | convert num(frozenTimePeriodInSecs)&lt;BR /&gt;
| convert ctime(endEpoch) AS endEvent | convert ctime(startEpoch) AS startEvent &lt;BR /&gt;
| eval shouldBeFrozen=if( ( state!="hot"  AND state!="thawed" ) AND toNow&amp;gt;frozenTimePeriodInSecs,"yes","no") &lt;BR /&gt;
| table index path id state startEvent endEvent shouldBeFrozen toNow frozenTimePeriodInSecs&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;for splunk 5 and 4, you have to manually add the values and do one index at a time&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;CODE&gt;|dbinspect index=main&lt;BR /&gt;
| eval frozenTimePeriodInSecs= 2592000&lt;BR /&gt;
| convert timeformat="%m/%d/%Y:%H:%M:%S" mktime(earliestTime)  AS endEpoch&lt;BR /&gt;
| eval toNow=now()-endEpoch | convert num(toNow) &lt;BR /&gt;
| convert num(frozenTimePeriodInSecs)&lt;BR /&gt;
| eval shouldBeFrozen=if( ( state!="hot"  AND state!="thawed" ) AND toNow&amp;gt;frozenTimePeriodInSecs,"yes","no") &lt;BR /&gt;
| table path id state earliestTime  latestTime endEvent shouldBeFrozen toNow frozenTimePeriodInSecs&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jan 2014 01:10:55 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2014-01-16T01:10:55Z</dc:date>
    <item>
      <title>bucket retention and frozenTimePeriodInSecs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116365#M24281</link>
      <description>&lt;P&gt;My index has a retention of 6 months with frozenTimePeriodInSecs=15552000. &lt;BR /&gt;
But I still see some events that are older than the retention.&lt;/P&gt;

&lt;P&gt;By example events that are from 6 month and 2 weeks.&lt;/P&gt;

&lt;P&gt;Any thoughts ?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2014 01:05:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116365#M24281</guid>
      <dc:creator>mataharry</dc:creator>
      <dc:date>2014-01-16T01:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: bucket retention and frozenTimePeriodInSecs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116366#M24282</link>
      <description>&lt;P&gt;A bucket that contains events overlapping the time retention will not be frozen until all the events are older than the retention.&lt;/P&gt;

&lt;P&gt;By default indexes.conf has buckets with up to 3 months of span. So It's possible that you have buckets still overlapping&lt;BR /&gt;
&lt;CODE&gt;[main]&lt;BR /&gt;
maxHotSpanSecs = 7776000&lt;BR /&gt;
frozenTimePeriodInSecs = 188697600&lt;BR /&gt;
&lt;/CODE&gt;&lt;BR /&gt;
A workaround may be to reduce the maxHotSpanSecs to a week, to force the buckets to be smaller, and rotate more often.&lt;/P&gt;

&lt;P&gt;To verify the status of your buckets, and estimate if they meet the condition to be frozen you can use those dbinspect searches on the indexer.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt; for Splunk 6, for all indexes with autodetection from frozenTimePeriodInSecs &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;CODE&gt;| dbinspect index=* | join index [|rest /services/data/indexes| eval index=title | table index frozenTimePeriodInSecs ] &lt;BR /&gt;
| eval toNow=now()-endEpoch | convert num(toNow) | convert num(frozenTimePeriodInSecs)&lt;BR /&gt;
| convert ctime(endEpoch) AS endEvent | convert ctime(startEpoch) AS startEvent &lt;BR /&gt;
| eval shouldBeFrozen=if( ( state!="hot"  AND state!="thawed" ) AND toNow&amp;gt;frozenTimePeriodInSecs,"yes","no") &lt;BR /&gt;
| table index path id state startEvent endEvent shouldBeFrozen toNow frozenTimePeriodInSecs&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;for splunk 5 and 4, you have to manually add the values and do one index at a time&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;CODE&gt;|dbinspect index=main&lt;BR /&gt;
| eval frozenTimePeriodInSecs= 2592000&lt;BR /&gt;
| convert timeformat="%m/%d/%Y:%H:%M:%S" mktime(earliestTime)  AS endEpoch&lt;BR /&gt;
| eval toNow=now()-endEpoch | convert num(toNow) &lt;BR /&gt;
| convert num(frozenTimePeriodInSecs)&lt;BR /&gt;
| eval shouldBeFrozen=if( ( state!="hot"  AND state!="thawed" ) AND toNow&amp;gt;frozenTimePeriodInSecs,"yes","no") &lt;BR /&gt;
| table path id state earliestTime  latestTime endEvent shouldBeFrozen toNow frozenTimePeriodInSecs&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2014 01:10:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116366#M24282</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2014-01-16T01:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: bucket retention and frozenTimePeriodInSecs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116367#M24283</link>
      <description>&lt;P&gt;I think the Splunk 5/4 search is wrong.  Wouldn't you want to make endEpoch as the &lt;EM&gt;latestTime&lt;/EM&gt; as every event in the bucket needs to be older than the frozenTimePeriod. If I run that search, I get 'yes' for buckets that have an earliestTime that is older than the frozenTimePeriod, but with a latestTime that is newer.  Those buckets wouldn't be deleted.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2014 23:45:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/bucket-retention-and-frozenTimePeriodInSecs/m-p/116367#M24283</guid>
      <dc:creator>hajducko</dc:creator>
      <dc:date>2014-04-10T23:45:38Z</dc:date>
    </item>
  </channel>
</rss>

