<?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: Why are indexes with hot/warm and cold paths on volumes showing as empty in dbinspect? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-indexes-with-hot-warm-and-cold-paths-on-volumes-showing/m-p/388542#M69573</link>
    <description>&lt;P&gt;So I might have answered this question with the help of Splunk support.  We'll know after our maintenance window this afternoon.&lt;/P&gt;

&lt;P&gt;In short, when we defined our volumes, we chose a path on the file system which contains a protected keyword which is present in code.  In our case, we chose &lt;EM&gt;/splunkdb-hot&lt;/EM&gt;.  And as it turns out, &lt;EM&gt;db-hot&lt;/EM&gt; used to be part of the name of hot buckets in older versions of Splunk.&lt;/P&gt;

&lt;P&gt;Will update again soon.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Apr 2019 16:01:34 GMT</pubDate>
    <dc:creator>brettwilliams</dc:creator>
    <dc:date>2019-04-05T16:01:34Z</dc:date>
    <item>
      <title>Why are indexes with hot/warm and cold paths on volumes showing as empty in dbinspect?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-indexes-with-hot-warm-and-cold-paths-on-volumes-showing/m-p/388541#M69572</link>
      <description>&lt;P&gt;This seems weird.  My index clusters (dev, qa, and production environments) seem to be completely ignoring my indexes configuration.&lt;/P&gt;

&lt;P&gt;The sizeOnDiskMB value for indexes in /opt/splunk shows values as expected.  And when I tweaked my indexes.conf, the cluster dutifully froze buckets.  But for indexes with hot/warm and cold volumes, sizeOnDeskMB is ZERO.  Weird.&lt;/P&gt;

&lt;P&gt;I'm on 7.0.7.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2019 21:47:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-indexes-with-hot-warm-and-cold-paths-on-volumes-showing/m-p/388541#M69572</guid>
      <dc:creator>brettwilliams</dc:creator>
      <dc:date>2019-04-02T21:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Why are indexes with hot/warm and cold paths on volumes showing as empty in dbinspect?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-indexes-with-hot-warm-and-cold-paths-on-volumes-showing/m-p/388542#M69573</link>
      <description>&lt;P&gt;So I might have answered this question with the help of Splunk support.  We'll know after our maintenance window this afternoon.&lt;/P&gt;

&lt;P&gt;In short, when we defined our volumes, we chose a path on the file system which contains a protected keyword which is present in code.  In our case, we chose &lt;EM&gt;/splunkdb-hot&lt;/EM&gt;.  And as it turns out, &lt;EM&gt;db-hot&lt;/EM&gt; used to be part of the name of hot buckets in older versions of Splunk.&lt;/P&gt;

&lt;P&gt;Will update again soon.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 16:01:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-indexes-with-hot-warm-and-cold-paths-on-volumes-showing/m-p/388542#M69573</guid>
      <dc:creator>brettwilliams</dc:creator>
      <dc:date>2019-04-05T16:01:34Z</dc:date>
    </item>
  </channel>
</rss>

