<?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: What is filling up dispatchtmp? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329222#M164563</link>
    <description>&lt;P&gt;Looks like it is adhoc search, can you please check on your all search head using command &lt;CODE&gt;ps -ef| grep -i splunk | grep search&lt;/CODE&gt; if any adhoc search is running which is trying to fetch too many events and running since long.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Dec 2017 15:57:01 GMT</pubDate>
    <dc:creator>harsmarvania57</dc:creator>
    <dc:date>2017-12-06T15:57:01Z</dc:date>
    <item>
      <title>What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329215#M164556</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;My /apps/splunk filesystem is filling up, and the culprit appears to be dispatchtmp.  What files go here?  It appears to be accelerated searches?  (Not sure).  How can I tell what search is associated with each directory created, and is there a way to route these tmp files elsewhere, as these are fixed disks.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 13:40:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329215#M164556</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-12-06T13:40:18Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329216#M164557</link>
      <description>&lt;P&gt;Hi @a212830,&lt;/P&gt;

&lt;P&gt;Based on &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.3/admin/Limitsconf"&gt;documentation&lt;/A&gt; it looks like storing temporary job files to distpatchtmp directory. Are you running search head pooling?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;use_dispatchtmp_dir = &amp;lt;bool&amp;gt;
* Specifies if the dispatchtmp directory should be used for temporary search 
  time files, to write temporary files to a different directory from the 
  dispatch directory for the job.
* Temp files are written to $SPLUNK_HOME/var/run/splunk/dispatchtmp/&amp;lt;sid&amp;gt;/ 
  directory.
* In search head pooling, performance can be improved by mounting dispatchtmp 
  to the local file system.
* Default: true, if search head pooling is enabled. Otherwise false.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 06 Dec 2017 13:54:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329216#M164557</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2017-12-06T13:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329217#M164558</link>
      <description>&lt;P&gt;Yes, we are running SHP. &lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 14:16:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329217#M164558</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-12-06T14:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329218#M164559</link>
      <description>&lt;P&gt;Based on this answer &lt;A href="https://answers.splunk.com/answers/73297/clean-dispatchtmp.html"&gt;https://answers.splunk.com/answers/73297/clean-dispatchtmp.html&lt;/A&gt; you can take down splunk and move content or clean that directory but I'll suggest to move somewhere else so you can restore if it will require.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 14:20:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329218#M164559</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2017-12-06T14:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329219#M164560</link>
      <description>&lt;P&gt;Thanks.  It appears that some of these jobs are generating content every minute, and I don't know why.  I looked at all the jobs associated in the app, and they run every hour. &lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 14:27:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329219#M164560</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-12-06T14:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329220#M164561</link>
      <description>&lt;P&gt;Can you please take &lt;CODE&gt;sid&lt;/CODE&gt; from dispatchtmp directory and try to find out that job in &lt;CODE&gt;_audit&lt;/CODE&gt; index, something like &lt;CODE&gt;index=_audit &amp;lt;sid&amp;gt;&lt;/CODE&gt;, if it will be scheduled search then you can check whether it is scheduled to run at every minute or not.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 14:30:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329220#M164561</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2017-12-06T14:30:31Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329221#M164562</link>
      <description>&lt;P&gt;There's only about 4 events for that sid, but my filesystem shows files getting generated every minute:&lt;/P&gt;

&lt;P&gt;1 splunk splunk   174131 Dec  6 01:36 statstmp_partition0_1512542219.16275.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   164979 Dec  6 01:36 statstmp_partition0_1512542219.16276.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   164752 Dec  6 01:36 statstmp_partition0_1512542219.16277.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   164121 Dec  6 01:37 statstmp_partition0_1512542219.16278.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   155234 Dec  6 01:37 statstmp_partition0_1512542220.16279.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   145870 Dec  6 01:37 statstmp_partition0_1512542220.16280.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   174143 Dec  6 01:37 statstmp_partition0_1512542220.16281.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   162143 Dec  6 01:37 statstmp_partition0_1512542220.16282.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   165256 Dec  6 01:37 statstmp_partition0_1512542220.16283.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   166296 Dec  6 01:37 statstmp_partition0_1512542220.16284.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   159039 Dec  6 01:37 statstmp_partition0_1512542220.16285.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   165745 Dec  6 01:37 statstmp_partition0_1512542220.16286.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   160583 Dec  6 01:37 statstmp_partition0_1512542221.16287.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   162555 Dec  6 01:37 statstmp_partition0_1512542221.16288.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   149885 Dec  6 01:37 statstmp_partition0_1512542221.16289.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   168065 Dec  6 01:37 statstmp_partition0_1512542221.16290.lrtp449.csv.gz&lt;BR /&gt;
-rw-------  1 splunk splunk   153648 Dec  6 01:37 statstmp_partition0_1512542221.16291.lrtp449.csv.gz&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:05:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329221#M164562</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2020-09-29T17:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329222#M164563</link>
      <description>&lt;P&gt;Looks like it is adhoc search, can you please check on your all search head using command &lt;CODE&gt;ps -ef| grep -i splunk | grep search&lt;/CODE&gt; if any adhoc search is running which is trying to fetch too many events and running since long.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 15:57:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329222#M164563</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2017-12-06T15:57:01Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329223#M164564</link>
      <description>&lt;P&gt;nothing that's been running for a long time.  &lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 18:24:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329223#M164564</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-12-06T18:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329224#M164565</link>
      <description>&lt;P&gt;At last I'll try rolling restart of search heads.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 02:56:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329224#M164565</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2017-12-07T02:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329225#M164566</link>
      <description>&lt;P&gt;To clarify, is &lt;CODE&gt;/apps/splunk&lt;/CODE&gt; your &lt;CODE&gt;$SPLUNK_HOME&lt;/CODE&gt;?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 13:19:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329225#M164566</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2017-12-07T13:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: What is filling up dispatchtmp?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329226#M164567</link>
      <description>&lt;P&gt;Someone owe me a beer if it turns out to be a real-time search running on all instances of the search head pool. lol&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 13:21:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-filling-up-dispatchtmp/m-p/329226#M164567</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2017-12-07T13:21:07Z</dc:date>
    </item>
  </channel>
</rss>

