<?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 is using the wrong disk for some reason - why ? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-is-using-the-wrong-disk-for-some-reason-why/m-p/203154#M23679</link>
    <description>&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/var/run/searchpeers&lt;/CODE&gt; stores bundles from your search heads used by the indexer to run searches for them with the appropriate configurations. Indexing happens elsewhere, by default in &lt;CODE&gt;$SPLUNK_HOME/var/lib/splunk&lt;/CODE&gt; - see if that's fairly small compared to what you've defined on your second drive to confirm that the index path setting is working.&lt;/P&gt;

&lt;P&gt;As for your searchpeers folder using 13GB, this can have several reasons:&lt;BR /&gt;
 - is your bundle huge, e.g. massive lookup files?&lt;BR /&gt;
 - do you have many search heads, each distributing different bundles? Consider merging the search heads into a search head cluster, reducing the number of different bundles on your indexers.&lt;BR /&gt;
 - are there old bundles from legacy search heads? These can be deleted.&lt;/P&gt;</description>
    <pubDate>Sat, 13 Feb 2016 13:24:10 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2016-02-13T13:24:10Z</dc:date>
    <item>
      <title>Splunk is using the wrong disk for some reason - why ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-is-using-the-wrong-disk-for-some-reason-why/m-p/203153#M23678</link>
      <description>&lt;P&gt;I have 2 drives - C and D on the indexer.&lt;BR /&gt;
I've defined the D drive for the indexing.&lt;BR /&gt;
yet Splunk Folder is using 19GB - I've noticed that the biggest folder is C:\Program Files\Splunk\var\run\searchpeers&lt;BR /&gt;
which uses 13GB.&lt;/P&gt;

&lt;P&gt;what am I missing here ?&lt;/P&gt;

&lt;P&gt;oh and this indexer is the licenser as well.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 12:07:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-is-using-the-wrong-disk-for-some-reason-why/m-p/203153#M23678</guid>
      <dc:creator>sbenamro</dc:creator>
      <dc:date>2016-02-13T12:07:12Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is using the wrong disk for some reason - why ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-is-using-the-wrong-disk-for-some-reason-why/m-p/203154#M23679</link>
      <description>&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/var/run/searchpeers&lt;/CODE&gt; stores bundles from your search heads used by the indexer to run searches for them with the appropriate configurations. Indexing happens elsewhere, by default in &lt;CODE&gt;$SPLUNK_HOME/var/lib/splunk&lt;/CODE&gt; - see if that's fairly small compared to what you've defined on your second drive to confirm that the index path setting is working.&lt;/P&gt;

&lt;P&gt;As for your searchpeers folder using 13GB, this can have several reasons:&lt;BR /&gt;
 - is your bundle huge, e.g. massive lookup files?&lt;BR /&gt;
 - do you have many search heads, each distributing different bundles? Consider merging the search heads into a search head cluster, reducing the number of different bundles on your indexers.&lt;BR /&gt;
 - are there old bundles from legacy search heads? These can be deleted.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 13:24:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-is-using-the-wrong-disk-for-some-reason-why/m-p/203154#M23679</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-02-13T13:24:10Z</dc:date>
    </item>
  </channel>
</rss>

