<?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: Cold rolling to frozen when it shouldn't? in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Cold-rolling-to-frozen-when-it-shouldn-t/m-p/75522#M8858</link>
    <description>&lt;P&gt;Support walked through a bunch of troubleshooting on this, only to find.... my syslog nightly maintenance script had a careless find command that included the Splunk Cold DB. That script was removing files every night. ARRG!&lt;/P&gt;

&lt;P&gt;Thanks Splunk support dudes, Josh and Octavio, for being patient and helpful.&lt;/P&gt;</description>
    <pubDate>Fri, 29 Apr 2011 19:51:02 GMT</pubDate>
    <dc:creator>twinspop</dc:creator>
    <dc:date>2011-04-29T19:51:02Z</dc:date>
    <item>
      <title>Cold rolling to frozen when it shouldn't?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Cold-rolling-to-frozen-when-it-shouldn-t/m-p/75521#M8857</link>
      <description>&lt;P&gt;My $SPLUNK_HOME/etc/system/local/indexes.conf is below. Apparently I'm missing something because cold archives are being dumped even though cold storage is currently only at 2 GB and /opt/splunk/var/lib/splunk/defaultdb is at 11 GB. Shouldn't maxTotalDataSizeMB and frozenTimePeriodInSecs be determining when cold storage rolls to frozen? Why is it being ignored?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
maxTotalDataSizeMB = 10000

[main]
coldPath = /syslog/splunk_archives
maxTotalDataSizeMB = 150000
maxHotBuckets = 10
maxDataSize = 500
# most warm buckets we can have is 30 =~ 15 GB
maxWarmDBCount = 30
# roll cold to frozen after 1 year
frozenTimePeriodInSecs = 31536000

# for summary index
[lgn-stats]
homePath = $SPLUNK_DB/lgn-stats/db
thawedPath = $SPLUNK_DB/lgn-stats/thaweddb
coldPath = $SPLUNK_DB/lgn-stats/colddb
maxTotalDataSizeMB = 1000
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I've promised the pointy-haired boss types we'd have at least 90 days of logs available, if not much more. I have 29 days and a LOT of empty disk space. Doh!&lt;/P&gt;

&lt;P&gt;Thanks,
jon&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2011 21:28:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Cold-rolling-to-frozen-when-it-shouldn-t/m-p/75521#M8857</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2011-04-06T21:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cold rolling to frozen when it shouldn't?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Cold-rolling-to-frozen-when-it-shouldn-t/m-p/75522#M8858</link>
      <description>&lt;P&gt;Support walked through a bunch of troubleshooting on this, only to find.... my syslog nightly maintenance script had a careless find command that included the Splunk Cold DB. That script was removing files every night. ARRG!&lt;/P&gt;

&lt;P&gt;Thanks Splunk support dudes, Josh and Octavio, for being patient and helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Apr 2011 19:51:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Cold-rolling-to-frozen-when-it-shouldn-t/m-p/75522#M8858</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2011-04-29T19:51:02Z</dc:date>
    </item>
  </channel>
</rss>

