<?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: Linux add disk space for Splunk  indexes and logs in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506266#M6391</link>
    <description>&lt;P&gt;Couple of best practices which we are using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Always use LVM and volume groups on linux =&amp;gt; You can extend space easily later one&lt;UL&gt;&lt;LI&gt;Add disk -&amp;gt; add it to vg -&amp;gt; extend current LV -&amp;gt; extend FS over that LV -&amp;gt; update indexes.conf to know bigger volume (if you are using volumes)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;xfs is your friends (at least in older linux versions we have had some issues with ext4)&lt;/LI&gt;&lt;LI&gt;On splunk side use always volumes (after that your life is easier)&lt;/LI&gt;&lt;LI&gt;As&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;said, use separate tiers for hot/warm and cold data&lt;/LI&gt;&lt;LI&gt;If you are using Smartstore then there are some other guidelines to follow, partially little bit different than using only local storage&lt;/LI&gt;&lt;LI&gt;Always ensure that your disks are fast enough!&lt;/LI&gt;&lt;LI&gt;For high volume indexes use maxDataSize = auto_high_volume&lt;/LI&gt;&lt;LI&gt;Add enough earlier new indexers not just additional disk space to current indexers.&lt;/LI&gt;&lt;LI&gt;Usually it's good to user clusters as earlier as possible (even one node clusters for future expansions).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jun 2020 08:44:29 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2020-06-26T08:44:29Z</dc:date>
    <item>
      <title>Linux add disk space for Splunk  indexes and logs</title>
      <link>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506238#M6389</link>
      <description>&lt;P&gt;Splunk Installation - I would like to know how to add disk space to splunk for indexes and logs.&amp;nbsp; Where would this be in the fine manual?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 02:55:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506238#M6389</guid>
      <dc:creator>jwilliams</dc:creator>
      <dc:date>2020-06-26T02:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Linux add disk space for Splunk  indexes and logs</title>
      <link>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506255#M6390</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/222997"&gt;@jwilliams&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;this isn't a Splunk problema: Splunk uses the disk space you give it.&lt;/P&gt;&lt;P&gt;To solve this problem you have to find in a Linux manual "lvextend" and it depends on the hardware you're using (virtual or physical.&lt;/P&gt;&lt;P&gt;Another solution to you problem could be adding another disk, so you can divide (in Splunk) indexes location in the two disks (using indexes.conf) or put the hot and warm buckets in the faster disk and cold buckets in the slower one (always using indexes.conf).&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 06:39:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506255#M6390</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-06-26T06:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Linux add disk space for Splunk  indexes and logs</title>
      <link>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506266#M6391</link>
      <description>&lt;P&gt;Couple of best practices which we are using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Always use LVM and volume groups on linux =&amp;gt; You can extend space easily later one&lt;UL&gt;&lt;LI&gt;Add disk -&amp;gt; add it to vg -&amp;gt; extend current LV -&amp;gt; extend FS over that LV -&amp;gt; update indexes.conf to know bigger volume (if you are using volumes)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;xfs is your friends (at least in older linux versions we have had some issues with ext4)&lt;/LI&gt;&lt;LI&gt;On splunk side use always volumes (after that your life is easier)&lt;/LI&gt;&lt;LI&gt;As&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;said, use separate tiers for hot/warm and cold data&lt;/LI&gt;&lt;LI&gt;If you are using Smartstore then there are some other guidelines to follow, partially little bit different than using only local storage&lt;/LI&gt;&lt;LI&gt;Always ensure that your disks are fast enough!&lt;/LI&gt;&lt;LI&gt;For high volume indexes use maxDataSize = auto_high_volume&lt;/LI&gt;&lt;LI&gt;Add enough earlier new indexers not just additional disk space to current indexers.&lt;/LI&gt;&lt;LI&gt;Usually it's good to user clusters as earlier as possible (even one node clusters for future expansions).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 08:44:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-add-disk-space-for-Splunk-indexes-and-logs/m-p/506266#M6391</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-06-26T08:44:29Z</dc:date>
    </item>
  </channel>
</rss>

