<?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 does &amp;quot;./splunk stop&amp;quot; do? in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/What-does-quot-splunk-stop-quot-do/m-p/442424#M3711</link>
    <description>&lt;P&gt;Don't &lt;CODE&gt;kill&lt;/CODE&gt; Splunk.  The &lt;CODE&gt;splunk stop&lt;/CODE&gt; command tells Splunk to shut down gracefully.  It waits for outstanding searches to complete before stopping.  If you pull the rug out from under splunkd you risk corrupting your data in the event a lookup file is being written or a bucket is being updated.&lt;/P&gt;</description>
    <pubDate>Fri, 09 Aug 2019 21:50:07 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-08-09T21:50:07Z</dc:date>
    <item>
      <title>What does "./splunk stop" do?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/What-does-quot-splunk-stop-quot-do/m-p/442423#M3710</link>
      <description>&lt;P&gt;My indexer takes a good 5+ minutes to stop, so I've been &lt;CODE&gt;pkill -f&lt;/CODE&gt;'ing it for the last year and a half. What does &lt;CODE&gt;./splunk stop&lt;/CODE&gt; do, how is a straight process kill different, and what am I risking?&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jun 2020 01:29:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/What-does-quot-splunk-stop-quot-do/m-p/442423#M3710</guid>
      <dc:creator>nick405060</dc:creator>
      <dc:date>2020-06-06T01:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: What does "./splunk stop" do?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/What-does-quot-splunk-stop-quot-do/m-p/442424#M3711</link>
      <description>&lt;P&gt;Don't &lt;CODE&gt;kill&lt;/CODE&gt; Splunk.  The &lt;CODE&gt;splunk stop&lt;/CODE&gt; command tells Splunk to shut down gracefully.  It waits for outstanding searches to complete before stopping.  If you pull the rug out from under splunkd you risk corrupting your data in the event a lookup file is being written or a bucket is being updated.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2019 21:50:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/What-does-quot-splunk-stop-quot-do/m-p/442424#M3711</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-08-09T21:50:07Z</dc:date>
    </item>
  </channel>
</rss>

