<?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 How do I never freeze data in an index? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-never-freeze-data-in-an-index/m-p/106489#M22429</link>
    <description>&lt;P&gt;I have one thread of data that we'd like to keep basically forever.  Over the past 8 years the log has only grown to 210MB so we definitely do not have a problem with size or space.&lt;/P&gt;

&lt;P&gt;I Splunk'd this log into it's own index, not mixed in with any other indexes so I could keep the retention settings different.  The index settings are (including the defaults):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;system     assureUTF8 = false
system     blockSignSize = 0
system     blockSignatureDatabase = _blocksignature
system     bucketRebuildMemoryHint = auto
system     coldPath = volume:cold1/gud
system     coldPath.maxDataSizeMB = 150000
system     coldToFrozenDir = 
system     coldToFrozenScript = 
system     compressRawdata = true
system     defaultDatabase = main
system     enableOnlineBucketRepair = true
system     enableRealtimeSearch = true
system     frozenTimePeriodInSecs = 188697600
system     homePath = volume:hot1/gud
system     homePath.maxDataSizeMB = 50000
system     indexThreads = auto
system     maxBloomBackfillBucketAge = 30d
system     maxConcurrentOptimizes = 3
system     maxDataSize = auto
system     maxHotBuckets = 3
system     maxHotIdleSecs = 0
system     maxHotSpanSecs = 7776000
system     maxMemMB = 5
system     maxMetaEntries = 1000000
system     maxRunningProcessGroups = 20
system     maxRunningProcessGroupsLowPriority = 1
system     maxTotalDataSizeMB = 500000
system     maxWarmDBCount = 300
system     memPoolMB = auto
system     minRawFileSyncSecs = disable
system     partialServiceMetaPeriod = 0
system     quarantineFutureSecs = 2592000
system     quarantinePastSecs = 77760000
system     rawChunkSizeBytes = 131072
system     rotatePeriodInSecs = 60
system     serviceMetaPeriod = 25
system     suppressBannerList = 
system     sync = 0
system     syncMeta = true
system     thawedPath = $SPLUNK_COLDDB/gud/thaweddb
system     throttleCheckPeriod = 15
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The problem is this index is deleting data older than about 120 days.  The total size of the index is 3MB right now.&lt;BR /&gt;
According to the way I read this configuration it should not freeze data until it reaches 50GB (homePath.maxDataSizeMB = 50000) or approximately 5.98 years old (frozenTimePeriodInSecs = 188697600).&lt;/P&gt;

&lt;P&gt;So why then is it deleting data from the index so soon?&lt;/P&gt;</description>
    <pubDate>Thu, 31 Jan 2013 15:50:52 GMT</pubDate>
    <dc:creator>pcjunkie</dc:creator>
    <dc:date>2013-01-31T15:50:52Z</dc:date>
    <item>
      <title>How do I never freeze data in an index?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-never-freeze-data-in-an-index/m-p/106489#M22429</link>
      <description>&lt;P&gt;I have one thread of data that we'd like to keep basically forever.  Over the past 8 years the log has only grown to 210MB so we definitely do not have a problem with size or space.&lt;/P&gt;

&lt;P&gt;I Splunk'd this log into it's own index, not mixed in with any other indexes so I could keep the retention settings different.  The index settings are (including the defaults):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;system     assureUTF8 = false
system     blockSignSize = 0
system     blockSignatureDatabase = _blocksignature
system     bucketRebuildMemoryHint = auto
system     coldPath = volume:cold1/gud
system     coldPath.maxDataSizeMB = 150000
system     coldToFrozenDir = 
system     coldToFrozenScript = 
system     compressRawdata = true
system     defaultDatabase = main
system     enableOnlineBucketRepair = true
system     enableRealtimeSearch = true
system     frozenTimePeriodInSecs = 188697600
system     homePath = volume:hot1/gud
system     homePath.maxDataSizeMB = 50000
system     indexThreads = auto
system     maxBloomBackfillBucketAge = 30d
system     maxConcurrentOptimizes = 3
system     maxDataSize = auto
system     maxHotBuckets = 3
system     maxHotIdleSecs = 0
system     maxHotSpanSecs = 7776000
system     maxMemMB = 5
system     maxMetaEntries = 1000000
system     maxRunningProcessGroups = 20
system     maxRunningProcessGroupsLowPriority = 1
system     maxTotalDataSizeMB = 500000
system     maxWarmDBCount = 300
system     memPoolMB = auto
system     minRawFileSyncSecs = disable
system     partialServiceMetaPeriod = 0
system     quarantineFutureSecs = 2592000
system     quarantinePastSecs = 77760000
system     rawChunkSizeBytes = 131072
system     rotatePeriodInSecs = 60
system     serviceMetaPeriod = 25
system     suppressBannerList = 
system     sync = 0
system     syncMeta = true
system     thawedPath = $SPLUNK_COLDDB/gud/thaweddb
system     throttleCheckPeriod = 15
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The problem is this index is deleting data older than about 120 days.  The total size of the index is 3MB right now.&lt;BR /&gt;
According to the way I read this configuration it should not freeze data until it reaches 50GB (homePath.maxDataSizeMB = 50000) or approximately 5.98 years old (frozenTimePeriodInSecs = 188697600).&lt;/P&gt;

&lt;P&gt;So why then is it deleting data from the index so soon?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2013 15:50:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-never-freeze-data-in-an-index/m-p/106489#M22429</guid>
      <dc:creator>pcjunkie</dc:creator>
      <dc:date>2013-01-31T15:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: How do I never freeze data in an index?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-never-freeze-data-in-an-index/m-p/106490#M22430</link>
      <description>&lt;P&gt;because a bucket roll to frozen when :&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;the bucket is not hot anymore&lt;/LI&gt;
&lt;LI&gt;AND  &lt;STRONG&gt;all the events in the buckets are older than the frozen time policy&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;This is very common if your buckets are new and small.&lt;/P&gt;

&lt;P&gt;FYI a hot bucket roll when it reaches :  maxHotSpanSecs, maxHotBuckets, maxDataSize (that depends of the system, and ca go tup to 10GB per bucket)&lt;/P&gt;

&lt;P&gt;use the&lt;CODE&gt;| dbinspect index=myindex&lt;/CODE&gt; to check the state of your buckets.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2013 16:13:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-never-freeze-data-in-an-index/m-p/106490#M22430</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2013-01-31T16:13:12Z</dc:date>
    </item>
  </channel>
</rss>

