<?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: Can you set a maximum hot index size globally? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-set-a-maximum-hot-index-size-globally/m-p/59870#M96876</link>
    <description>&lt;P&gt;You can make use of volume notation in indexes.conf for hot and warm. Note that hot and warm should be on the same path. As usual, there is more info here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/indexesconf&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;indexes.conf&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;&lt;CODE&gt;[volume:hot1]&lt;BR /&gt;
path = /mnt/fast_disk&lt;BR /&gt;
maxVolumeDataSizeMB = 100000&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[volume:cold1]&lt;BR /&gt;
path = /mnt/big_disk&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[idx1]&lt;BR /&gt;
homePath = volume:hot1/idx1&lt;BR /&gt;
coldPath = volume:cold1/idx1&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[idx2]&lt;BR /&gt;
homePath = volume:hot1/idx2&lt;BR /&gt;
coldPath = volume:cold1/idx2&lt;/CODE&gt;&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;Hope it helps&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;please upvote if you find this answer useful&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 25 May 2012 00:14:01 GMT</pubDate>
    <dc:creator>_d_</dc:creator>
    <dc:date>2012-05-25T00:14:01Z</dc:date>
    <item>
      <title>Can you set a maximum hot index size globally?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-set-a-maximum-hot-index-size-globally/m-p/59869#M96875</link>
      <description>&lt;P&gt;We would like to use a combination of solid state drives for the hot index and slower, cheaper disk for the warm/cold buckets.  Is there a way to tell Splunk that the total size of all hot indexes should not exceed a certain size and roll events when that size is reached?  &lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Thu, 24 May 2012 22:18:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-you-set-a-maximum-hot-index-size-globally/m-p/59869#M96875</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2012-05-24T22:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: Can you set a maximum hot index size globally?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-set-a-maximum-hot-index-size-globally/m-p/59870#M96876</link>
      <description>&lt;P&gt;You can make use of volume notation in indexes.conf for hot and warm. Note that hot and warm should be on the same path. As usual, there is more info here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/indexesconf&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;indexes.conf&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;&lt;CODE&gt;[volume:hot1]&lt;BR /&gt;
path = /mnt/fast_disk&lt;BR /&gt;
maxVolumeDataSizeMB = 100000&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[volume:cold1]&lt;BR /&gt;
path = /mnt/big_disk&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[idx1]&lt;BR /&gt;
homePath = volume:hot1/idx1&lt;BR /&gt;
coldPath = volume:cold1/idx1&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[idx2]&lt;BR /&gt;
homePath = volume:hot1/idx2&lt;BR /&gt;
coldPath = volume:cold1/idx2&lt;/CODE&gt;&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;Hope it helps&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;please upvote if you find this answer useful&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2012 00:14:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-you-set-a-maximum-hot-index-size-globally/m-p/59870#M96876</guid>
      <dc:creator>_d_</dc:creator>
      <dc:date>2012-05-25T00:14:01Z</dc:date>
    </item>
  </channel>
</rss>

