<?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: Splunk summery volume in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-summery-volume/m-p/568900#M8614</link>
    <description>&lt;P&gt;Let's see in the docs:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;maxVolumeDataSizeMB = &amp;lt;positive integer&amp;gt;
* If set, this setting limits the total size of all databases that reside
  on this volume to the maximum size specified, in MB.  Note that this it
  will act only on those indexes which reference this volume, not on the
  total size of the path set in the 'path' setting of this volume.&lt;/LI-CODE&gt;&lt;P&gt;In other words, the limit for your COLD volume limits only cumulative size of databases directly referencing this volume. The _splunk_summaries volume has its own independent limit. So effectively you may grow your /Splunk-Storage/COLD directory up to 4674000MB (probably a bit more, considering some metadata overhead and so on)&lt;/P&gt;</description>
    <pubDate>Wed, 29 Sep 2021 09:20:42 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2021-09-29T09:20:42Z</dc:date>
    <item>
      <title>Splunk summery volume</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-summery-volume/m-p/568896#M8613</link>
      <description>&lt;P&gt;Hi Splunkers! I hope you all are doing well.&lt;/P&gt;&lt;P&gt;This is my indexes.conf&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="indexes.jpg" style="width: 860px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/16197i0C9E0196CD937E15/image-size/large?v=v2&amp;amp;px=999" role="button" title="indexes.jpg" alt="indexes.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;My problem is that the COLD volume was fulled.&lt;/P&gt;&lt;P&gt;This is the output of df command&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="df.jpg" style="width: 959px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/16196i46E9913DE593E124/image-size/large?v=v2&amp;amp;px=999" role="button" title="df.jpg" alt="df.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The fs of COLD volume is xfs&lt;/P&gt;&lt;P&gt;Do you know that the total maxsize of both COLD and splunk_summareis must not exceed from total space or Just setting the COLD volume is enough because the splunk_summaries volume is part of that?&lt;/P&gt;&lt;P&gt;I mean in my case Splunk set the addition of both &lt;SPAN&gt;volume:COLD and &lt;/SPAN&gt;&lt;SPAN&gt;volume:_splunk_summaries for total space for storing buckets or just set the maxVolumesize of volume:COLD config?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;Thanks in advance for any advice&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PS: I know Splunk do recommend that the summaries must be stored in HOT volume!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 08:22:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-summery-volume/m-p/568896#M8613</guid>
      <dc:creator>m_zandinia</dc:creator>
      <dc:date>2021-09-29T08:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk summery volume</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-summery-volume/m-p/568900#M8614</link>
      <description>&lt;P&gt;Let's see in the docs:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;maxVolumeDataSizeMB = &amp;lt;positive integer&amp;gt;
* If set, this setting limits the total size of all databases that reside
  on this volume to the maximum size specified, in MB.  Note that this it
  will act only on those indexes which reference this volume, not on the
  total size of the path set in the 'path' setting of this volume.&lt;/LI-CODE&gt;&lt;P&gt;In other words, the limit for your COLD volume limits only cumulative size of databases directly referencing this volume. The _splunk_summaries volume has its own independent limit. So effectively you may grow your /Splunk-Storage/COLD directory up to 4674000MB (probably a bit more, considering some metadata overhead and so on)&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 09:20:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-summery-volume/m-p/568900#M8614</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2021-09-29T09:20:42Z</dc:date>
    </item>
  </channel>
</rss>

