<?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 indexes.conf and volume settings in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335609#M62065</link>
    <description>&lt;P&gt;I have a volume defined:&lt;/P&gt;

&lt;P&gt;[volume:hot]&lt;BR /&gt;
path = /indexes/warm&lt;BR /&gt;
maxVolumeDataSizeMB = 2097152&lt;/P&gt;

&lt;P&gt;[test]&lt;BR /&gt;
homePath=volume:hot/test/db&lt;BR /&gt;
coldPath=volume:cold/test/colddb&lt;BR /&gt;
thawedPath=/indexes/cold/test/thaweddb&lt;BR /&gt;
repFactor=autotestmaxDataSize = auto_high_volume&lt;/P&gt;

&lt;P&gt;So ... I'd like this 'test' index to not be controlled by the 2Tb volume size limit, but I don't want to move it to another filesystem. The index is small, and I'd like to let it be grow to &amp;gt; 10Gb before it starts rolling over to cold ...&lt;/P&gt;

&lt;P&gt;can I create another volume (on the same path)&lt;/P&gt;

&lt;P&gt;[volume:test]&lt;BR /&gt;
path = /indexes/warm&lt;BR /&gt;
maxVolumeDataSizeMB = 10000&lt;/P&gt;

&lt;P&gt;[test]&lt;BR /&gt;
homePath=volume:test/test/db&lt;BR /&gt;
coldPath=volume:test/test/colddb&lt;BR /&gt;
thawedPath=/indexes/cold/test/thaweddb&lt;BR /&gt;
repFactor=autotestmaxDataSize = auto_high_volume&lt;/P&gt;

&lt;P&gt;Would that configuration make it so, when /indexes/warm reaches 2Tb, it will start moving older buckets to cold without touching the 'test' index?&lt;/P&gt;

&lt;P&gt;Or, will this entirely mess things up.&lt;/P&gt;

&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 15:05:51 GMT</pubDate>
    <dc:creator>pkeller</dc:creator>
    <dc:date>2020-09-29T15:05:51Z</dc:date>
    <item>
      <title>indexes.conf and volume settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335609#M62065</link>
      <description>&lt;P&gt;I have a volume defined:&lt;/P&gt;

&lt;P&gt;[volume:hot]&lt;BR /&gt;
path = /indexes/warm&lt;BR /&gt;
maxVolumeDataSizeMB = 2097152&lt;/P&gt;

&lt;P&gt;[test]&lt;BR /&gt;
homePath=volume:hot/test/db&lt;BR /&gt;
coldPath=volume:cold/test/colddb&lt;BR /&gt;
thawedPath=/indexes/cold/test/thaweddb&lt;BR /&gt;
repFactor=autotestmaxDataSize = auto_high_volume&lt;/P&gt;

&lt;P&gt;So ... I'd like this 'test' index to not be controlled by the 2Tb volume size limit, but I don't want to move it to another filesystem. The index is small, and I'd like to let it be grow to &amp;gt; 10Gb before it starts rolling over to cold ...&lt;/P&gt;

&lt;P&gt;can I create another volume (on the same path)&lt;/P&gt;

&lt;P&gt;[volume:test]&lt;BR /&gt;
path = /indexes/warm&lt;BR /&gt;
maxVolumeDataSizeMB = 10000&lt;/P&gt;

&lt;P&gt;[test]&lt;BR /&gt;
homePath=volume:test/test/db&lt;BR /&gt;
coldPath=volume:test/test/colddb&lt;BR /&gt;
thawedPath=/indexes/cold/test/thaweddb&lt;BR /&gt;
repFactor=autotestmaxDataSize = auto_high_volume&lt;/P&gt;

&lt;P&gt;Would that configuration make it so, when /indexes/warm reaches 2Tb, it will start moving older buckets to cold without touching the 'test' index?&lt;/P&gt;

&lt;P&gt;Or, will this entirely mess things up.&lt;/P&gt;

&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:05:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335609#M62065</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2020-09-29T15:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: indexes.conf and volume settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335610#M62066</link>
      <description>&lt;P&gt;This won't work ,  you can't have two stanza for same volume.  Using  two separate volumes for this would be best. &lt;/P&gt;

&lt;P&gt;Also check out maxWarmDBCount option for your index.&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.0/Admin/Indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.0/Admin/Indexesconf&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2017 07:06:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335610#M62066</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2017-07-28T07:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: indexes.conf and volume settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335611#M62067</link>
      <description>&lt;P&gt;Thank you. Much appreciated, and it's kinda what I figured ... but had to ask. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2017 14:16:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/indexes-conf-and-volume-settings/m-p/335611#M62067</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2017-07-28T14:16:52Z</dc:date>
    </item>
  </channel>
</rss>

