<?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: Rolling upgrade vs Maintenance mode commands on cluster manager and indexers in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705869#M116745</link>
    <description>&lt;P&gt;Enabling maintenance mode simply tells the Cluster Manager to not bother doing bucket fix-ups.&amp;nbsp; Nothing happens on the indexers themselves.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;upgrade-init&lt;/FONT&gt; command starts a rolling restart of the indexers after setting maintenance mode.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Dec 2024 18:27:02 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2024-12-03T18:27:02Z</dc:date>
    <item>
      <title>Rolling upgrade vs Maintenance mode commands on cluster manager and indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705861#M116741</link>
      <description>&lt;P&gt;I’ve read the documentation on these commands, executed both in a dev environment and observed the behavior.&lt;/P&gt;&lt;P&gt;My interpretation of the commands is that they are the same.&lt;/P&gt;&lt;P&gt;Does someone want to take a stab, and try to better explain them from your own perspective &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please don't point&amp;nbsp;me or reference to any Splunk docs, I've read them already and still can't see when is the best use case to use these. I want to read you're opinion!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;What is the main difference between these two commands?&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;splunk enable maintenance-mode&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;splunk upgrade-init cluster-peers &lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Here is the scene: I will be upgrading a cluster of splunk cluster manager and their peers.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Cluster manager&lt;/LI&gt;&lt;LI&gt;Indexers&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I don't want to initiate a bucket fixup on each indexer (10 peers * 10TB on each peer).&lt;/P&gt;&lt;P&gt;Which one best fits/servers my use case above?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 16:39:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705861#M116741</guid>
      <dc:creator>rickymckenzie10</dc:creator>
      <dc:date>2024-12-03T16:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: Rolling upgrade vs Maintenance mode commands on cluster manager and indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705869#M116745</link>
      <description>&lt;P&gt;Enabling maintenance mode simply tells the Cluster Manager to not bother doing bucket fix-ups.&amp;nbsp; Nothing happens on the indexers themselves.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;upgrade-init&lt;/FONT&gt; command starts a rolling restart of the indexers after setting maintenance mode.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 18:27:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705869#M116745</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-12-03T18:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: Rolling upgrade vs Maintenance mode commands on cluster manager and indexers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705870#M116746</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/265393"&gt;@rickymckenzie10&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;for your requirement, I would suggest to go for option 2 for upgarde&lt;/P&gt;&lt;P&gt;let me explain difference as per my understanding&amp;nbsp;&lt;/P&gt;&lt;P&gt;in most of the terms both works same but some differences.&lt;/P&gt;&lt;P&gt;with Maintenance mode&amp;nbsp; you are telling cluster master that&amp;nbsp;&lt;BR /&gt;some activity&amp;nbsp;will happen on the indexers, it can be stopping splunk on indexer, rebooting the server , upgrading Splunk .&lt;/P&gt;&lt;P&gt;With&amp;nbsp;Maintenance mode enabled bucket replication will not happen in the entire cluster&amp;nbsp;&lt;BR /&gt;once&amp;nbsp;maintenance mode disabled, bucket fixup tasks will complete.&lt;/P&gt;&lt;P&gt;With&amp;nbsp;Rolling upgrade command , manager node understands that&amp;nbsp;its upgrade&amp;nbsp;of cluster and with running&amp;nbsp;Rolling upgrade command also enables maintenance&amp;nbsp;mode and tries to minimize the impact to searches.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 18:30:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/m-p/705870#M116746</guid>
      <dc:creator>SanjayReddy</dc:creator>
      <dc:date>2024-12-03T18:30:17Z</dc:date>
    </item>
  </channel>
</rss>

