<?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 restart for configuration change in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81542#M20672</link>
    <description>&lt;P&gt;As per the splunk documentation We should use the below approach:&lt;/P&gt;

&lt;P&gt;splunk rolling-restart cluster-peers&lt;/P&gt;

&lt;P&gt;_&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Restartthecluster"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Restartthecluster&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2013 12:53:40 GMT</pubDate>
    <dc:creator>linu1988</dc:creator>
    <dc:date>2013-07-17T12:53:40Z</dc:date>
    <item>
      <title>Splunk restart for configuration change</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81540#M20670</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;
We have a master with peers configuration. When we do a configuration change in the indexer we need to restart. All the changes go on correctly. But after sometime we get a message that the Indexer may be down. In alerts we also get " Unable to distribute to peer named Server:8089 at uri Server:8089 because peer has status = "Down" ".&lt;/P&gt;

&lt;P&gt;So what is the correct way to restart/ how can we solve this issue in distributed environment?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 08:15:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81540#M20670</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2013-07-02T08:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk restart for configuration change</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81541#M20671</link>
      <description>&lt;P&gt;Thank you for the reply. I was talking about the indexers where its acting as search peers. If i create an index i have to restart the splunkd service alone in that particular server. Will the "splunk reload deploy-client" command able to do the job for me?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 08:51:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81541#M20671</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2013-07-02T08:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk restart for configuration change</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81542#M20672</link>
      <description>&lt;P&gt;As per the splunk documentation We should use the below approach:&lt;/P&gt;

&lt;P&gt;splunk rolling-restart cluster-peers&lt;/P&gt;

&lt;P&gt;_&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Restartthecluster"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Restartthecluster&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2013 12:53:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-restart-for-configuration-change/m-p/81542#M20672</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2013-07-17T12:53:40Z</dc:date>
    </item>
  </channel>
</rss>

