<?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: maxTotalDataSizeMB max value or 0 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59562#M11744</link>
    <description>&lt;P&gt;might be Splunk will auto-tune itself to go with the highest priority fields ?! not sure...&lt;BR /&gt;
But, i hope that Splunk wont delete the data , it makes the index size to grow till max size&lt;/P&gt;

&lt;P&gt;maxTotalDataSizeMB&lt;BR /&gt;
frozenTimePeriodInSecs&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jun 2013 14:50:19 GMT</pubDate>
    <dc:creator>chimbudp</dc:creator>
    <dc:date>2013-06-25T14:50:19Z</dc:date>
    <item>
      <title>maxTotalDataSizeMB max value or 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59560#M11742</link>
      <description>&lt;P&gt;Can you set maxTotalDataSizeMB to 0, or optionally set it to an incredibly high number (90000000, or 90TB) in order to hopefully make the cold-to-frozen process only happen based on frozenTimePeriodInSecs.  Basically time based retention instead of the maxTotalDataSizeMB?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
--adam&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2011 19:37:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59560#M11742</guid>
      <dc:creator>adamw</dc:creator>
      <dc:date>2011-08-17T19:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: maxTotalDataSizeMB max value or 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59561#M11743</link>
      <description>&lt;P&gt;Per the docs for &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/admin/Indexesconf"&gt;indexes.conf&lt;/A&gt;, the maximum value is 4294967295 MB. Setting it that high would result in time-only retention.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 13:34:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59561#M11743</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-06-25T13:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: maxTotalDataSizeMB max value or 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59562#M11744</link>
      <description>&lt;P&gt;might be Splunk will auto-tune itself to go with the highest priority fields ?! not sure...&lt;BR /&gt;
But, i hope that Splunk wont delete the data , it makes the index size to grow till max size&lt;/P&gt;

&lt;P&gt;maxTotalDataSizeMB&lt;BR /&gt;
frozenTimePeriodInSecs&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 14:50:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/maxTotalDataSizeMB-max-value-or-0/m-p/59562#M11744</guid>
      <dc:creator>chimbudp</dc:creator>
      <dc:date>2013-06-25T14:50:19Z</dc:date>
    </item>
  </channel>
</rss>

