<?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 Search Head Cluster Upgrade in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761024#M29951</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/317134"&gt;@himanshu2&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;please don't call people in questions!&lt;/P&gt;&lt;P&gt;Anyway, following the documentation, it's a known issue, you must follow the documentation during upgrade from 9.3.x to 9.4.x:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/administer-the-app-key-value-store/upgrade-the-kv-store-server-version" target="_blank"&gt;https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/administer-the-app-key-value-store/upgrade-the-kv-store-server-version&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2026 10:41:20 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2026-05-18T10:41:20Z</dc:date>
    <item>
      <title>Splunk Search Head Cluster Upgrade</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761009#M29947</link>
      <description>&lt;P&gt;I have a 2 search heads in a Splunk SH cluster in the dev environment. Recently, I upgraded Splunk from 9.3.8 to 9.4.11 version but kvstore didn't came up which I believe most probably due to Splunk restart in between /both Splunk SHs were stopped at the same time during upgrade activity.&lt;BR /&gt;&lt;BR /&gt;TO resolve kvstore issues, I took backup of mongo from /opt/splunk/var/lib/splunk/kvstore/ and then restarted Splunk in both the servers as well, but nothing helped.&lt;BR /&gt;&lt;BR /&gt;I disabled kvstore because it was not getting upgraded to 7.0.28 version. Now, when I checked SH Cluster status, for one of the SH, it is stuck at&amp;nbsp;&lt;STRONG&gt;last_conf_replication : Pending.&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;I understand, we should have at least 3 SHs in a cluster but this is for testing purposes only and it was working fine with 2 SHs in the past.&amp;nbsp;&lt;BR /&gt;How can I resolve the SH Cluster and kvstore issues in this case?&lt;BR /&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="himanshu2_0-1779087834120.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/42062i7D5378676C9AE723/image-size/medium?v=v2&amp;amp;px=400" role="button" title="himanshu2_0-1779087834120.png" alt="himanshu2_0-1779087834120.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The mongod.log contents in the SH, where I don't see pending status&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="himanshu2_1-1779088000598.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/42063iDC2DFF64CED4F422/image-size/medium?v=v2&amp;amp;px=400" role="button" title="himanshu2_1-1779088000598.png" alt="himanshu2_1-1779088000598.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 12:00:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761009#M29947</guid>
      <dc:creator>himanshu2</dc:creator>
      <dc:date>2026-05-18T12:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Search Head Cluster Upgrade</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761024#M29951</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/317134"&gt;@himanshu2&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;please don't call people in questions!&lt;/P&gt;&lt;P&gt;Anyway, following the documentation, it's a known issue, you must follow the documentation during upgrade from 9.3.x to 9.4.x:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/administer-the-app-key-value-store/upgrade-the-kv-store-server-version" target="_blank"&gt;https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/administer-the-app-key-value-store/upgrade-the-kv-store-server-version&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 10:41:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761024#M29951</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2026-05-18T10:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Search Head Cluster Upgrade</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761057#M29953</link>
      <description>&lt;P&gt;Sorry, but this didn't work.&lt;BR /&gt;&lt;BR /&gt;I tried everything but still kvstore is not upgraded. It has probably something to do with just two search heads in the cluster, but I am not really sure.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2026 10:30:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Search-Head-Cluster-Upgrade/m-p/761057#M29953</guid>
      <dc:creator>himanshu2</dc:creator>
      <dc:date>2026-05-19T10:30:39Z</dc:date>
    </item>
  </channel>
</rss>

