<?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 Why do we get &amp;quot;not Ready for searchable rolling restart&amp;quot;? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/556489#M18922</link>
    <description>&lt;P&gt;We have a 8.1.2 dployment with 2 clustered indexers and a search head cluster. We have two master nodes, one is operational, the other is on stand-by.&lt;/P&gt;
&lt;P&gt;When I run splunk show cluster-status --verbose on the master node I get all positive answers except for this one: "Ready for searchable rolling restart NO".&lt;/P&gt;
&lt;P&gt;It is not explained in the documentation what is behind this check.&lt;/P&gt;
&lt;P&gt;Does anyone know what could be the matter?&lt;/P&gt;
&lt;P&gt;splunk show cluster-status --verbose&lt;/P&gt;
&lt;P&gt;Pre-flight check successful .................. YES&lt;BR /&gt;Replication factor met ............... YES&lt;BR /&gt;Search factor met .................... YES&lt;BR /&gt;All data is searchable ............... YES&lt;BR /&gt;All peers are up ..................... YES&lt;BR /&gt;CM version is compatible ............. YES&lt;BR /&gt;No fixup tasks in progress ........... YES&lt;BR /&gt;Splunk version peer count { 8.1.2: 2 }&lt;BR /&gt;Ready for searchable rolling restart NO&lt;/P&gt;
&lt;P&gt;Indexing Ready YES&lt;/P&gt;
&lt;P&gt;idx14 6XYZ1234-9877-4911-A73E-XYZ12345FC43 default&lt;BR /&gt;Searchable YES&lt;BR /&gt;Status Up&lt;BR /&gt;Bucket Count=314&lt;BR /&gt;Splunk Version=8.1.2&lt;/P&gt;
&lt;P&gt;idx13 DXYZ1234-8765-4DA5-BD4F-XYZ12345B8DF default&lt;BR /&gt;Searchable YES&lt;BR /&gt;Status Up&lt;BR /&gt;Bucket Count=316&lt;BR /&gt;Splunk Version=8.1.2&lt;/P&gt;
&lt;P&gt;_audit&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=124&lt;BR /&gt;Size=41491951&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;122/124 122/124&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;122/124 122/124&lt;/P&gt;
&lt;P&gt;_internal&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=115&lt;BR /&gt;Size=3672105501&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;115/115 115/115&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;115/115 115/115&lt;/P&gt;
&lt;P&gt;_telemetry&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=18&lt;BR /&gt;Size=67083&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;18/18 18/18&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;18/18 18/18&lt;/P&gt;
&lt;P&gt;main&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=57&lt;BR /&gt;Size=6295363&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;57/57 57/57&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;57/57 57/57&lt;/P&gt;</description>
    <pubDate>Thu, 13 Oct 2022 14:20:20 GMT</pubDate>
    <dc:creator>Marlan</dc:creator>
    <dc:date>2022-10-13T14:20:20Z</dc:date>
    <item>
      <title>Why do we get "not Ready for searchable rolling restart"?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/556489#M18922</link>
      <description>&lt;P&gt;We have a 8.1.2 dployment with 2 clustered indexers and a search head cluster. We have two master nodes, one is operational, the other is on stand-by.&lt;/P&gt;
&lt;P&gt;When I run splunk show cluster-status --verbose on the master node I get all positive answers except for this one: "Ready for searchable rolling restart NO".&lt;/P&gt;
&lt;P&gt;It is not explained in the documentation what is behind this check.&lt;/P&gt;
&lt;P&gt;Does anyone know what could be the matter?&lt;/P&gt;
&lt;P&gt;splunk show cluster-status --verbose&lt;/P&gt;
&lt;P&gt;Pre-flight check successful .................. YES&lt;BR /&gt;Replication factor met ............... YES&lt;BR /&gt;Search factor met .................... YES&lt;BR /&gt;All data is searchable ............... YES&lt;BR /&gt;All peers are up ..................... YES&lt;BR /&gt;CM version is compatible ............. YES&lt;BR /&gt;No fixup tasks in progress ........... YES&lt;BR /&gt;Splunk version peer count { 8.1.2: 2 }&lt;BR /&gt;Ready for searchable rolling restart NO&lt;/P&gt;
&lt;P&gt;Indexing Ready YES&lt;/P&gt;
&lt;P&gt;idx14 6XYZ1234-9877-4911-A73E-XYZ12345FC43 default&lt;BR /&gt;Searchable YES&lt;BR /&gt;Status Up&lt;BR /&gt;Bucket Count=314&lt;BR /&gt;Splunk Version=8.1.2&lt;/P&gt;
&lt;P&gt;idx13 DXYZ1234-8765-4DA5-BD4F-XYZ12345B8DF default&lt;BR /&gt;Searchable YES&lt;BR /&gt;Status Up&lt;BR /&gt;Bucket Count=316&lt;BR /&gt;Splunk Version=8.1.2&lt;/P&gt;
&lt;P&gt;_audit&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=124&lt;BR /&gt;Size=41491951&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;122/124 122/124&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;122/124 122/124&lt;/P&gt;
&lt;P&gt;_internal&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=115&lt;BR /&gt;Size=3672105501&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;115/115 115/115&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;115/115 115/115&lt;/P&gt;
&lt;P&gt;_telemetry&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=18&lt;BR /&gt;Size=67083&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;18/18 18/18&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;18/18 18/18&lt;/P&gt;
&lt;P&gt;main&lt;BR /&gt;Number of non-site aware buckets=0&lt;BR /&gt;Number of buckets=57&lt;BR /&gt;Size=6295363&lt;BR /&gt;Searchable YES&lt;BR /&gt;Replicated copies tracker&lt;BR /&gt;57/57 57/57&lt;BR /&gt;Searchable copies tracker&lt;BR /&gt;57/57 57/57&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 14:20:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/556489#M18922</guid>
      <dc:creator>Marlan</dc:creator>
      <dc:date>2022-10-13T14:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/557663#M18945</link>
      <description>&lt;P&gt;You have an even number of indexers in your cluster, and only two. If one of your indexers goes down (fails or restarts) then your data will not be searchable.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jun 2021 18:45:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/557663#M18945</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2021-06-29T18:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/557754#M18950</link>
      <description>&lt;P&gt;Thanks for you reply.&lt;/P&gt;&lt;P&gt;Our indexes are fully replicated with a search factor of 2, so even if one indexer is down, data should be searchable after primary buckets have been re-assigned to the running indexer. A searchable rolling restart should do precisely that in advance of restarting the indexers, one at a time.&lt;/P&gt;&lt;P&gt;I cannot see why it should not work in our system.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.1.2/Indexer/Userollingrestart" target="_self"&gt;https://docs.splunk.com/Documentation/Splunk/8.1.2/Indexer/Userollingrestart&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, the documentation offers no insight into the check that results in:&lt;BR /&gt;"Ready for searchable rolling restart NO"&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2021 07:09:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/557754#M18950</guid>
      <dc:creator>Marlan</dc:creator>
      <dc:date>2021-06-30T07:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616930#M26221</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231770"&gt;@Marlan&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;did you try to perform a rolling restart and if yes, did it work without downtime?&lt;/P&gt;&lt;P&gt;We have the same setup and are considerung to conduct a rolling upgrade of the cluster with only two indexers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 08:22:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616930#M26221</guid>
      <dc:creator>hrngr</dc:creator>
      <dc:date>2022-10-13T08:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616934#M26222</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Usually it's better to create a new questions than use an old one.&lt;/P&gt;&lt;P&gt;What I have seen is that when the one has done rolling-restart for peers there is short time when previous node is not yet fully functional and the next one has started the restart. For that time when you have only two indexer, even with SF=2, all buckets (actually any in this case) are not searchable. I'm not sure how many nodes you must have to get working searchable rolling restart. My guess is that you should have at least 3 peer with SF=3, but haven't try this.&lt;/P&gt;&lt;P&gt;r. Ismo&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 08:31:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616934#M26222</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-10-13T08:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616937#M26223</link>
      <description>&lt;P&gt;Thanks. So in the case of a rolling upgrade that would be fine, because then it's in our hands to take down the second peer only after the first one is fully functional again.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 08:43:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616937#M26223</guid>
      <dc:creator>hrngr</dc:creator>
      <dc:date>2022-10-13T08:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why do we get not Ready for searchable rolling restart</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616946#M26224</link>
      <description>&lt;P&gt;Exactly that way.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 09:05:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-do-we-get-quot-not-Ready-for-searchable-rolling-restart-quot/m-p/616946#M26224</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-10-13T09:05:39Z</dc:date>
    </item>
  </channel>
</rss>

