<?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 6.3 not compatible with cluster 6.2? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264096#M10039</link>
    <description>&lt;P&gt;I think that is expected.  This is an excerpt from the doc linked below (see the second item):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;For master nodes running Splunk Enterprise version 6.2 and above
Peer nodes and search heads can run different versions from the master, subject to these restrictions:

 The peer nodes and search heads must run version 6.1 or above.
 The peer nodes and search heads must run the same or a lower version than the master node.
 The peer nodes and search heads within a site must all run the same version.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/Indexer/Systemrequirements#Splunk_Enterprise_version_compatibility" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/Indexer/Systemrequirements#Splunk_Enterprise_version_compatibility&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The upgrade documentation is out there as well.  I think it says you need to take the entire cluster down to do the upgrade, but that's a bit insane.  There is another recent question out here somewhere about a similar downtime concern.  &lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 07:33:11 GMT</pubDate>
    <dc:creator>maciep</dc:creator>
    <dc:date>2020-09-29T07:33:11Z</dc:date>
    <item>
      <title>Search head 6.3 not compatible with cluster 6.2?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264095#M10038</link>
      <description>&lt;P&gt;We have a cluster (master node + search indexers) and a few standalone search heads both running on 6.2.1. The other day I upgraded one of the search heads to 6.3. After upgrade the search head was not able to connect to the cluster anymore.&lt;/P&gt;

&lt;P&gt;Is this expected (search head on 6.3 won't work with cluster on 6.2)?&lt;BR /&gt;
To upgrade everything to 6.3 what is the correct order / procedure (would like to have minimal down time) ?&lt;/P&gt;

&lt;P&gt;Thx for the pointers.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 13:36:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264095#M10038</guid>
      <dc:creator>rozmar564</dc:creator>
      <dc:date>2015-10-12T13:36:19Z</dc:date>
    </item>
    <item>
      <title>Re: Search head 6.3 not compatible with cluster 6.2?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264096#M10039</link>
      <description>&lt;P&gt;I think that is expected.  This is an excerpt from the doc linked below (see the second item):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;For master nodes running Splunk Enterprise version 6.2 and above
Peer nodes and search heads can run different versions from the master, subject to these restrictions:

 The peer nodes and search heads must run version 6.1 or above.
 The peer nodes and search heads must run the same or a lower version than the master node.
 The peer nodes and search heads within a site must all run the same version.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/Indexer/Systemrequirements#Splunk_Enterprise_version_compatibility" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/Indexer/Systemrequirements#Splunk_Enterprise_version_compatibility&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The upgrade documentation is out there as well.  I think it says you need to take the entire cluster down to do the upgrade, but that's a bit insane.  There is another recent question out here somewhere about a similar downtime concern.  &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:33:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264096#M10039</guid>
      <dc:creator>maciep</dc:creator>
      <dc:date>2020-09-29T07:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Search head 6.3 not compatible with cluster 6.2?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264097#M10040</link>
      <description>&lt;P&gt;Great - this answers my question - thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 16:00:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264097#M10040</guid>
      <dc:creator>rozmar564</dc:creator>
      <dc:date>2015-10-12T16:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Search head 6.3 not compatible with cluster 6.2?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264098#M10041</link>
      <description>&lt;P&gt;Makes it difficult when you have a larger or more complex install.  Trying to resync multiple nodes across a wan at the same time makes your network admins cry.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 16:02:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264098#M10041</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2015-10-12T16:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Search head 6.3 not compatible with cluster 6.2?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264099#M10042</link>
      <description>&lt;P&gt;I did upgrades before - from 5.x to 6.x and from 6.x to 6.2 - its not that bad, but our business goes nuts even for 5 minutes of "outage", but I guess they just have to cope for a half hour or so.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 16:03:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-head-6-3-not-compatible-with-cluster-6-2/m-p/264099#M10042</guid>
      <dc:creator>rozmar564</dc:creator>
      <dc:date>2015-10-12T16:03:57Z</dc:date>
    </item>
  </channel>
</rss>

