<?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: How to restart a SHC (search head cluster) at the server level? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130695#M4960</link>
    <description>&lt;P&gt;This should have appeared as a reply to "sowings".&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jun 2017 18:20:09 GMT</pubDate>
    <dc:creator>IamaRobot</dc:creator>
    <dc:date>2017-06-06T18:20:09Z</dc:date>
    <item>
      <title>How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130687#M4952</link>
      <description>&lt;P&gt;I am at a client where, by policy, they must restart servers every week. They have an 8-node Search Head Cluster. What is the best method for restarting it?&lt;/P&gt;

&lt;P&gt;(Is there a maintenance mode, such as indexer clustering? Do they need to run any command before/after the restart? Should they restart 1, 2, 3, 8 at a time?)&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 10:40:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130687#M4952</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2015-05-29T10:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130688#M4953</link>
      <description>&lt;P&gt;There is no maintenance mode in SHC. The nodes can be restarted in any order you want. It's a question of whether you want to maintain availability during the restart process. If availability is not required, then you can restart them all at once. &lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 13:52:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130688#M4953</guid>
      <dc:creator>mahamed_splunk</dc:creator>
      <dc:date>2015-05-29T13:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130689#M4954</link>
      <description>&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/RestartSHC"&gt;http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/RestartSHC&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 14:01:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130689#M4954</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2015-05-29T14:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130690#M4955</link>
      <description>&lt;P&gt;Great - thanks. Restarting them all servers at once will not cause unnecessary replication, assuming that some may come back online before others?&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 14:04:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130690#M4955</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2015-05-29T14:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130691#M4956</link>
      <description>&lt;P&gt;I need to know how to restart the servers themselves, not run a rolling restart on the Splunk instances.&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 14:04:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130691#M4956</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2015-05-29T14:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130692#M4957</link>
      <description>&lt;P&gt;Splunk won't trigger a restart of the host OS. Maintenance mode is not required, because the SHC is a bit less paranoid about satisfying replication of the artifacts. We're not talking about &lt;EM&gt;data fidelity&lt;/EM&gt;, we're talking about cached copies of the searches that have been run. If you're talking about replication of knowledge objects, that will always happen across all nodes.&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 14:11:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130692#M4957</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2015-05-29T14:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130693#M4958</link>
      <description>&lt;P&gt;Yes. I'm saying a restart of the host OS is required by policy, and I needed to know the best way to do it for the clustered search heads. It sounds like all at once is sufficient.&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2015 14:18:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130693#M4958</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2015-05-29T14:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130694#M4959</link>
      <description>&lt;P&gt;This is a link to the docs, but the docs don't address this question.  We want to know if rolling restarts perform what I would call a "graceful" restart.  For a good description of how a graceful restart should work see this description from Apache &lt;A href="https://httpd.apache.org/docs/2.4/stopping.html#graceful"&gt;https://httpd.apache.org/docs/2.4/stopping.html#graceful&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;Users would expect a graceful restart to dis allow new searches, but allow currently running searches to finish before restarting. &lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 18:19:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130694#M4959</guid>
      <dc:creator>IamaRobot</dc:creator>
      <dc:date>2017-06-06T18:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130695#M4960</link>
      <description>&lt;P&gt;This should have appeared as a reply to "sowings".&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 18:20:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/130695#M4960</guid>
      <dc:creator>IamaRobot</dc:creator>
      <dc:date>2017-06-06T18:20:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to restart a SHC (search head cluster) at the server level?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/671966#M27775</link>
      <description>&lt;P&gt;To perform rolling restart of SH cluster use,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;splunk rolling-restart shcluster-members&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;To check the current status of rolling restart use,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;splunk rolling-restart shcluster-members -status 1&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 19:54:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-restart-a-SHC-search-head-cluster-at-the-server-level/m-p/671966#M27775</guid>
      <dc:creator>pkumar9610</dc:creator>
      <dc:date>2023-12-14T19:54:32Z</dc:date>
    </item>
  </channel>
</rss>

