<?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: Search Head Clustering SHC - Push config, restart myself? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234585#M69705</link>
    <description>&lt;P&gt;When you push a configuration, it will enforce an automatic rolling restart. This is by design. If you're time constrained on maintenance windows, you should be pushing the configuration and restarting during that time window.&lt;/P&gt;

&lt;P&gt;One thing you might consider is adjusting is the percent of SH's that are restarted during the rolling restart. By default, this value is 10% of the total number of SHs in the cluster. You could reduce this to maybe 5%...&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.0/DistSearch/RestartSHC#Configure_the_number_of_members_that_restart_simultaneously"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.0/DistSearch/RestartSHC#Configure_the_number_of_members_that_restart_simultaneously&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 09 May 2016 03:37:15 GMT</pubDate>
    <dc:creator>esix_splunk</dc:creator>
    <dc:date>2016-05-09T03:37:15Z</dc:date>
    <item>
      <title>Search Head Clustering SHC - Push config, restart myself?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234583#M69703</link>
      <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;Is there a way to push a config from a deployer to the search head cluster, then retart the members on my own time?  &lt;/P&gt;

&lt;P&gt;Background: &lt;BR /&gt;
We currently have a 24 node search head cluster and are largely happy. Except we are not receiving complaints we restart too often. I was hoping I could restart them one at a time, waiting for the other to come into service before doing the next. A rolling restart so users won't be impacted as much.  I see the rolling restart optipn for the SHC. But I don't see an option to push fro the deployer and wait. &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 08 May 2016 20:40:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234583#M69703</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2016-05-08T20:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Clustering SHC - Push config, restart myself?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234584#M69704</link>
      <description>&lt;P&gt;I'm trying to follow you here but it's a bit confusing.  &lt;/P&gt;

&lt;P&gt;Is it true that you want to do a delayed rolling restart? Perhaps you want to schedule the restart for 1am, etc?&lt;/P&gt;</description>
      <pubDate>Sun, 08 May 2016 23:27:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234584#M69704</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-05-08T23:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Clustering SHC - Push config, restart myself?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234585#M69705</link>
      <description>&lt;P&gt;When you push a configuration, it will enforce an automatic rolling restart. This is by design. If you're time constrained on maintenance windows, you should be pushing the configuration and restarting during that time window.&lt;/P&gt;

&lt;P&gt;One thing you might consider is adjusting is the percent of SH's that are restarted during the rolling restart. By default, this value is 10% of the total number of SHs in the cluster. You could reduce this to maybe 5%...&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.0/DistSearch/RestartSHC#Configure_the_number_of_members_that_restart_simultaneously"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.0/DistSearch/RestartSHC#Configure_the_number_of_members_that_restart_simultaneously&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2016 03:37:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234585#M69705</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2016-05-09T03:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Clustering SHC - Push config, restart myself?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234586#M69706</link>
      <description>&lt;P&gt;You can always schedule the restart via crontab for whatever time you like...&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2016 04:31:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Clustering-SHC-Push-config-restart-myself/m-p/234586#M69706</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-05-10T04:31:11Z</dc:date>
    </item>
  </channel>
</rss>

