<?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: Disk space was full need to delete the data ? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-was-full-need-to-delete-the-data/m-p/599028#M104464</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/179309"&gt;@naveenyadav99&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;at first, the delete command perform a logical deletion (events are marked as deleted but remain in the index), so you don't have new space in your storage.&lt;/P&gt;&lt;P&gt;Then the delete command requires that the user has a "can_delete" role.&lt;/P&gt;&lt;P&gt;Anyway, the problem is that you haven't sufficient space in your disk, so every search is blocked, and you cannot perform a search for deleting events.&lt;/P&gt;&lt;P&gt;To restart your searches, you can modify the minimun disk space from 5 MB to 2 MB [Settings -- Server Settings -- General Settings], but, as I said, this doesn't resolve your problem, it's only a momentary solution.&lt;/P&gt;&lt;P&gt;You can physically delete the oldest buckets, modifying the retention of some large index (e.g. _internal), you can do this, modifying indexes.conf on $SPLUNK_HOME/etc/system/local/indexes.conf, adding&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;FrozenTimePeriodInSecs = 864000&lt;/LI-CODE&gt;&lt;P&gt;and restarting Splunk.&lt;/P&gt;&lt;P&gt;If you haven't indexes.conf in local folder, as you well know, you have to create it in this folder, don't modify the one in default because at the first upgrade you loose this change.&lt;/P&gt;&lt;P&gt;This should give you much space on your disk but you'll have Splunk internal data only for 10 days.&lt;/P&gt;&lt;P&gt;Obviously you loose some information as the license consuption after 10 days.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Tue, 24 May 2022 08:52:58 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-05-24T08:52:58Z</dc:date>
    <item>
      <title>Disk space was full need to delete the data ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-was-full-need-to-delete-the-data/m-p/599026#M104463</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am facing disk space issue in my Splunk so decided to delete the unwanted data as it is test environment, while running the following command &lt;STRONG&gt;index=malware | delete&amp;nbsp;&lt;/STRONG&gt;i am getting the following error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Search not executed: The minimum free disk space (5000MB) reached for /opt/splunk/var/run/splunk/dispatch. user=admin., concurrency_category="historical", concurrency_context="user_instance-wide", current_concurrency=0, concurrency_limit=5000&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;and also I can see so many errors on my Splunk as follows&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="naveenyadav99_0-1653380950367.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/19791i48C5E2E306CAEBC7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="naveenyadav99_0-1653380950367.png" alt="naveenyadav99_0-1653380950367.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help me on this to solve the issues.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 08:34:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Disk-space-was-full-need-to-delete-the-data/m-p/599026#M104463</guid>
      <dc:creator>naveenyadav99</dc:creator>
      <dc:date>2022-05-24T08:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space was full need to delete the data ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-was-full-need-to-delete-the-data/m-p/599028#M104464</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/179309"&gt;@naveenyadav99&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;at first, the delete command perform a logical deletion (events are marked as deleted but remain in the index), so you don't have new space in your storage.&lt;/P&gt;&lt;P&gt;Then the delete command requires that the user has a "can_delete" role.&lt;/P&gt;&lt;P&gt;Anyway, the problem is that you haven't sufficient space in your disk, so every search is blocked, and you cannot perform a search for deleting events.&lt;/P&gt;&lt;P&gt;To restart your searches, you can modify the minimun disk space from 5 MB to 2 MB [Settings -- Server Settings -- General Settings], but, as I said, this doesn't resolve your problem, it's only a momentary solution.&lt;/P&gt;&lt;P&gt;You can physically delete the oldest buckets, modifying the retention of some large index (e.g. _internal), you can do this, modifying indexes.conf on $SPLUNK_HOME/etc/system/local/indexes.conf, adding&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;FrozenTimePeriodInSecs = 864000&lt;/LI-CODE&gt;&lt;P&gt;and restarting Splunk.&lt;/P&gt;&lt;P&gt;If you haven't indexes.conf in local folder, as you well know, you have to create it in this folder, don't modify the one in default because at the first upgrade you loose this change.&lt;/P&gt;&lt;P&gt;This should give you much space on your disk but you'll have Splunk internal data only for 10 days.&lt;/P&gt;&lt;P&gt;Obviously you loose some information as the license consuption after 10 days.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 08:52:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Disk-space-was-full-need-to-delete-the-data/m-p/599028#M104464</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-05-24T08:52:58Z</dc:date>
    </item>
  </channel>
</rss>

