<?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: Why does /opt/splunk/var/run/searchpeers fill up? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293861#M55874</link>
    <description>&lt;P&gt;what version of Splunk are you running?&lt;/P&gt;</description>
    <pubDate>Wed, 22 Nov 2017 19:52:49 GMT</pubDate>
    <dc:creator>rphillips_splk</dc:creator>
    <dc:date>2017-11-22T19:52:49Z</dc:date>
    <item>
      <title>Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293859#M55872</link>
      <description>&lt;P&gt;On two indexers &lt;CODE&gt;/opt/splunk/var/run/searchpeers&lt;/CODE&gt; is at 20 GBs of files with delta files and bundle file. Is it safe to delete them?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 18:12:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293859#M55872</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-11-22T18:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293860#M55873</link>
      <description>&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/203076/searchpeers-folder-filling-up-optsplunkwhat-could.html"&gt;searchpeers folder filling up /opt/splunk..what could be the cause??&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;speaks about it. Is it safe to delete them?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 18:17:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293860#M55873</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-11-22T18:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293861#M55874</link>
      <description>&lt;P&gt;what version of Splunk are you running?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 19:52:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293861#M55874</guid>
      <dc:creator>rphillips_splk</dc:creator>
      <dc:date>2017-11-22T19:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293862#M55875</link>
      <description>&lt;P&gt;You can. The search heads will resend latest knowledge bundles again. For query performance/impact to users, I would say do it during a maintenance period/off-office hours.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 20:33:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293862#M55875</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-11-22T20:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293863#M55876</link>
      <description>&lt;P&gt;We just upgraded last night from 6.5.2. to 6.6.2. I wonder whether the upgrade has anything to do with this behavior ..&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 22:14:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293863#M55876</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-11-22T22:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293864#M55877</link>
      <description>&lt;P&gt;Perfect. Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 22:14:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293864#M55877</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-11-22T22:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293865#M55878</link>
      <description>&lt;P&gt;You may be hitting a known bug which can cause this issue. I would consider upgrading to one of the versions listed below and see if that resolves the issue.&lt;/P&gt;

&lt;P&gt;BUG: &lt;CODE&gt;SPL-140831&lt;/CODE&gt; "Splunk not cleaning up $SPLUNK_HOME/var/run/searchpeers of .delta files and matching directories whose only non-empty subdirectory has the .index extension"&lt;/P&gt;

&lt;P&gt;Fixed in: 6.5.6+, 6.6.3+, 7.0.0+&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 23:10:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293865#M55878</guid>
      <dc:creator>rphillips_splk</dc:creator>
      <dc:date>2017-11-22T23:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293866#M55879</link>
      <description>&lt;P&gt;Much appreciated - we'll upgrade tonight. &lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 17:02:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293866#M55879</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-11-27T17:02:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293867#M55880</link>
      <description>&lt;P&gt;Could you please elaborate on this topic, even I have the same issue storing a lot of bundle and delta files in searchpeers. And we are running 6.6.3. Is it ok to delete those files from search peers? If not what is the best way to reduce the size. Few of them shows more than 900+Mb in size. This causing this error message &lt;/P&gt;

&lt;P&gt;"Bundle Replication: Problem replicating config (bundle) to search peer ' xxxx:8089 ', Reading reply to upload: rv=-2, Receive from=&lt;A href="https://xxxx:8089"&gt;https://xxxx:8089&lt;/A&gt; timed out; exceeded 60sec, as per=distsearch.conf/[replicationSettings]/sendRcvTimeout"&lt;/P&gt;

&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jan 2018 01:19:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293867#M55880</guid>
      <dc:creator>vinaykata</dc:creator>
      <dc:date>2018-01-03T01:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293868#M55881</link>
      <description>&lt;P&gt;The error indicating timeout while replicating search bundles is likely unrelated to the question asked previously.&lt;/P&gt;

&lt;P&gt;In your case a larger bundle size may just be taking longer than Splunk expects to replicate out to the search peers.  This may have been recently triggered by the search bundle growing due to a new app or lookup, or even just network slowness.&lt;/P&gt;

&lt;P&gt;The bundles themselves are just tar files.  You can copy one to a temporary directory and untar it to see which, if any, knowledge objects are unnecessarily large.  Lookup files are a likely culprit.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jan 2018 04:17:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293868#M55881</guid>
      <dc:creator>micahkemp</dc:creator>
      <dc:date>2018-01-03T04:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293869#M55882</link>
      <description>&lt;P&gt;I am facing the same issue in 7.0.2.&lt;/P&gt;

&lt;P&gt;I have been doing the following things but this only seems to be temporary solution for a few days.&lt;BR /&gt;
1. Stop splunkd and delete the bundles from searchpeer directory.&lt;BR /&gt;
2. Data rebalance from Cluster Master.&lt;/P&gt;

&lt;P&gt;Kindly advise, if anything else can be done.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Oct 2018 22:38:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293869#M55882</guid>
      <dc:creator>kamal_jagga</dc:creator>
      <dc:date>2018-10-23T22:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293870#M55883</link>
      <description>&lt;P&gt;Same. Having this problem and I'm on 7.1 so I'm going to open a ticket with support.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 20:32:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293870#M55883</guid>
      <dc:creator>trav271</dc:creator>
      <dc:date>2019-01-14T20:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293871#M55884</link>
      <description>&lt;P&gt;I am seeing it in 7.3.1&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2019 17:45:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293871#M55884</guid>
      <dc:creator>jcastro20111</dc:creator>
      <dc:date>2019-08-26T17:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293872#M55885</link>
      <description>&lt;P&gt;We're also seeing this issue in Splunk 7.2.1. IDX Cluster size = 41 Nodes with $SPLUNK_HOME FS size of 40GB. the Search Peers dir keeps getting up to 25-30GB which triggers the dispatch dir warning about there being less than X amount of size left on the disk. Frustrating. &lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2020 19:17:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/293872#M55885</guid>
      <dc:creator>joshualemoine</dc:creator>
      <dc:date>2020-02-10T19:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/516782#M87461</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/157483"&gt;@trav271&lt;/a&gt;&amp;nbsp;&amp;nbsp;What answer do I give you support?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Aug 2020 17:36:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/516782#M87461</guid>
      <dc:creator>splunkcol</dc:creator>
      <dc:date>2020-08-28T17:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Why does /opt/splunk/var/run/searchpeers fill up?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/517140#M87515</link>
      <description>&lt;P&gt;version 8.0.5&lt;/P&gt;&lt;P&gt;Could someone indicate what they are for or what they do and if they can be deleted or not?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="splunkcol_0-1598922592367.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10581i6DBBAFD36390BE59/image-size/medium?v=v2&amp;amp;px=400" role="button" title="splunkcol_0-1598922592367.png" alt="splunkcol_0-1598922592367.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 01:10:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-opt-splunk-var-run-searchpeers-fill-up/m-p/517140#M87515</guid>
      <dc:creator>splunkcol</dc:creator>
      <dc:date>2020-09-01T01:10:42Z</dc:date>
    </item>
  </channel>
</rss>

