<?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: managing per index data retention in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268979#M51647</link>
    <description>&lt;P&gt;Indexes consume most of the disk space. If you run out of disk space, the indexer stops indexing.&lt;BR /&gt;
You can set a minimum free space limit to control how low free disk space falls&lt;BR /&gt;
before indexing stops. Indexing resumes once space exceeds the minimum.&lt;/P&gt;

&lt;P&gt;Note:&lt;BR /&gt;
. The indexer does not clear any of its disk space with this method. It simply&lt;BR /&gt;
pauses until more space becomes available.&lt;BR /&gt;
· Incoming data can be lost while indexing is suspended.&lt;/P&gt;

&lt;P&gt;When a volume containing warm buckets reaches its maxVolumeDataSizeMB, it&lt;BR /&gt;
starts rolling buckets to cold. When a volume containing cold buckets reaches its&lt;BR /&gt;
maxVolumeDataSizeMB, it starts rolling buckets to frozen. If a volume contains both&lt;BR /&gt;
warm and cold buckets (which will happen if an index's homePath and coldPath&lt;BR /&gt;
are both set to the same volume), the oldest bucket will be rolled to frozen.&lt;/P&gt;</description>
    <pubDate>Fri, 22 Jul 2016 09:26:48 GMT</pubDate>
    <dc:creator>inventsekar</dc:creator>
    <dc:date>2016-07-22T09:26:48Z</dc:date>
    <item>
      <title>managing per index data retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268976#M51644</link>
      <description>&lt;P&gt;I need to retain data for 6 months with 400 GB of data max in warm and 5 tb in cold. Will the below work? I am confused since when I use the DMC to review index stats I see index usage described as 488.12/488.28. Does that mean that the index will start dropping data at 488.28? Thanks!&lt;/P&gt;

&lt;P&gt;[default]&lt;/P&gt;

&lt;H1&gt;Default for each index. Can be overridden per index based upon the volume of data received by that index.&lt;/H1&gt;

&lt;H1&gt;400GB&lt;/H1&gt;

&lt;P&gt;homePath.maxDataSizeMB = 409600&lt;/P&gt;

&lt;H1&gt;5TB&lt;/H1&gt;

&lt;P&gt;coldPath.maxDataSizeMB = 5120000&lt;/P&gt;

&lt;H1&gt;Custom Indexes&lt;/H1&gt;

&lt;P&gt;[ie]&lt;BR /&gt;
homePath = $SPLUNK_DB/ie/db&lt;BR /&gt;
coldPath = /shared/splunk/var/lib/splunk/ie/colddb&lt;BR /&gt;
thawedPath = $SPLUNK_DB/ie/thaweddb&lt;BR /&gt;
frozenTimePeriodInSecs = 15552000&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:17:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268976#M51644</guid>
      <dc:creator>ebaileytu</dc:creator>
      <dc:date>2020-09-29T10:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: managing per index data retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268977#M51645</link>
      <description>&lt;P&gt;think you have to set &lt;EM&gt;maxTotalDataSizeMB = xxxxxxxxx&lt;/EM&gt; &lt;BR /&gt;
Youre setting are still the default. &lt;/P&gt;

&lt;P&gt;As far as I understand it will start dropping data on whatever limit is fit first. &lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 08:49:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268977#M51645</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2016-07-22T08:49:52Z</dc:date>
    </item>
    <item>
      <title>Re: managing per index data retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268978#M51646</link>
      <description>&lt;H1&gt;400GB&lt;/H1&gt;

&lt;P&gt;homePath.maxDataSizeMB = 400000 --- (did you mistype it as "409600" ah?!?!)&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 09:10:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268978#M51646</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2016-07-22T09:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: managing per index data retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268979#M51647</link>
      <description>&lt;P&gt;Indexes consume most of the disk space. If you run out of disk space, the indexer stops indexing.&lt;BR /&gt;
You can set a minimum free space limit to control how low free disk space falls&lt;BR /&gt;
before indexing stops. Indexing resumes once space exceeds the minimum.&lt;/P&gt;

&lt;P&gt;Note:&lt;BR /&gt;
. The indexer does not clear any of its disk space with this method. It simply&lt;BR /&gt;
pauses until more space becomes available.&lt;BR /&gt;
· Incoming data can be lost while indexing is suspended.&lt;/P&gt;

&lt;P&gt;When a volume containing warm buckets reaches its maxVolumeDataSizeMB, it&lt;BR /&gt;
starts rolling buckets to cold. When a volume containing cold buckets reaches its&lt;BR /&gt;
maxVolumeDataSizeMB, it starts rolling buckets to frozen. If a volume contains both&lt;BR /&gt;
warm and cold buckets (which will happen if an index's homePath and coldPath&lt;BR /&gt;
are both set to the same volume), the oldest bucket will be rolled to frozen.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 09:26:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268979#M51647</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2016-07-22T09:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: managing per index data retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268980#M51648</link>
      <description>&lt;P&gt;ok - that makes sense. I need to define the overall size along with the size for home and cold so data is shifted to cold to account for limits in main storage.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 13:00:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/managing-per-index-data-retention/m-p/268980#M51648</guid>
      <dc:creator>ebaileytu</dc:creator>
      <dc:date>2016-07-22T13:00:27Z</dc:date>
    </item>
  </channel>
</rss>

