<?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 Disk space issue in indexer in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Disk-space-issue-in-indexer/m-p/225988#M23802</link>
    <description>&lt;P&gt;I ran out of disk space in one of the indexer its total size is 5Tb ,at present the size 4.9Tb &lt;/P&gt;

&lt;P&gt;inside the "splogs" these are the directories which are consuming more space&lt;BR /&gt;
208G syslogs &lt;BR /&gt;
402G unix_bsm &lt;BR /&gt;
173G unix_ldap &lt;BR /&gt;
249G webops_appcd&lt;BR /&gt;
278G win_svrs &lt;BR /&gt;
290G net_proxy&lt;BR /&gt;
494G summarydb&lt;/P&gt;

&lt;P&gt;So can we delete the data inside it ? if so we delete will there be any impact as they are other 3 indexers in the environment along with this current one ? rest all indexers are doing good .&lt;/P&gt;

&lt;P&gt;how to find master node and slave node !&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 10:01:59 GMT</pubDate>
    <dc:creator>Kaushikkatta03</dc:creator>
    <dc:date>2020-09-29T10:01:59Z</dc:date>
    <item>
      <title>Disk space issue in indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Disk-space-issue-in-indexer/m-p/225988#M23802</link>
      <description>&lt;P&gt;I ran out of disk space in one of the indexer its total size is 5Tb ,at present the size 4.9Tb &lt;/P&gt;

&lt;P&gt;inside the "splogs" these are the directories which are consuming more space&lt;BR /&gt;
208G syslogs &lt;BR /&gt;
402G unix_bsm &lt;BR /&gt;
173G unix_ldap &lt;BR /&gt;
249G webops_appcd&lt;BR /&gt;
278G win_svrs &lt;BR /&gt;
290G net_proxy&lt;BR /&gt;
494G summarydb&lt;/P&gt;

&lt;P&gt;So can we delete the data inside it ? if so we delete will there be any impact as they are other 3 indexers in the environment along with this current one ? rest all indexers are doing good .&lt;/P&gt;

&lt;P&gt;how to find master node and slave node !&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:01:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Disk-space-issue-in-indexer/m-p/225988#M23802</guid>
      <dc:creator>Kaushikkatta03</dc:creator>
      <dc:date>2020-09-29T10:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space issue in indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Disk-space-issue-in-indexer/m-p/225989#M23803</link>
      <description>&lt;P&gt;Good information at - &lt;A href="https://answers.splunk.com/answers/210811/how-to-free-up-disk-space.html"&gt;How to free up disk space?&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;chanfoli says there -&lt;/P&gt;

&lt;P&gt;-- You can safely delete cold and warm buckets with splunk stopped, understanding that you will loose the data contained in any deleted bucket. If you set your aging/size policies appropriately, splunk should roll to frozen (which by default, actually means delete) at some point soon after this config is picked up, but I have always handled such cases by deleting cold buckets.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2016 14:39:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Disk-space-issue-in-indexer/m-p/225989#M23803</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-06-23T14:39:24Z</dc:date>
    </item>
  </channel>
</rss>

