<?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 Cluster captain election fails with error -NOT_LEADER CURRENT_STATE = FOLLOWER in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216042#M63366</link>
    <description>&lt;P&gt;Here is what worked::::&lt;/P&gt;

&lt;P&gt;1) Stop all 5 SHC members.&lt;BR /&gt;
2)lean _raft on all nodes &amp;gt; $SPLUNK_HOME/var/run/splunk/_raft. NOTE: It needs to be cleaned from all nodes.&lt;BR /&gt;
3) restart all 5 SHC members&lt;BR /&gt;
6)We initially bootstrapped one member&lt;/P&gt;

&lt;P&gt;Bootstrap one node using command like below and then added peers using add peer on the captain bootstrapped&lt;/P&gt;

&lt;P&gt;splunk bootstrap shcluster-captain -servers_list ":" -auth :&lt;/P&gt;

&lt;P&gt;Here the reference to add peer:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/DistSearch/Addaclustermember#Add_the_instance" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/DistSearch/Addaclustermember#Add_the_instance&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 08:19:16 GMT</pubDate>
    <dc:creator>sat94541</dc:creator>
    <dc:date>2020-09-29T08:19:16Z</dc:date>
    <item>
      <title>Search Head Cluster captain election fails with error -NOT_LEADER CURRENT_STATE = FOLLOWER</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216040#M63364</link>
      <description>&lt;P&gt;We have 5 Node SHC member on splunk version 6.3.  The Captain election is not suceeding.&lt;BR /&gt;
We followed steps and cleared _raft and that did not help.&lt;BR /&gt;
Steps that were taken are &lt;/P&gt;

&lt;P&gt;1) Stop all SHC members.&lt;BR /&gt;
2)Clean _raft on all nodes &amp;gt; $SPLUNK_HOME/var/run/splunk/_raft&lt;BR /&gt;
3)restart all members&lt;BR /&gt;
4)Attempted to bootstraped all using command &lt;/P&gt;

&lt;P&gt;splunk bootstrap shcluster-captain -servers_list "&amp;lt;URI&amp;gt;:&amp;lt;management_port&amp;gt;,&amp;lt;URI&amp;gt;:&amp;lt;management_port&amp;gt;,..." -auth &amp;lt;username&amp;gt;:&amp;lt;password&amp;gt;&lt;/P&gt;

&lt;P&gt;This failed with error SHPRaftConsensus - NOT_LEADER CURRENT_STATE = FOLLOWER&lt;/P&gt;

&lt;P&gt;teh Splunkd.log has the folloing entries&lt;/P&gt;

&lt;P&gt;01-05-2016 19:35:53.658 -0500 INFO ServerConfig - My server name is "test5421.xx.test.com".&lt;BR /&gt;
01-05-2016 19:35:53.659 -0500 INFO ServerConfig - My hostname is "test5421".&lt;BR /&gt;
01-05-2016 19:40:37.058 -0500 INFO SHPRaftConsensus - stepDown(1)&lt;BR /&gt;
01-05-2016 19:40:37.058 -0500 INFO SHPRaftConsensus - Activating configuration 1:\n&amp;lt;configuration&amp;gt;\n&amp;lt;prev_configuration&amp;gt;\n&amp;lt;server&amp;gt;\n&amp;lt;server_id&amp;gt;&lt;A href="https://test5421.xx.test.com:8089" target="_blank"&gt;https://test5421.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.430 -0500 INFO SHPRaftConsensus - Running for election in term 2&lt;BR /&gt;
01-05-2016 19:41:03.431 -0500 INFO SHPRaftConsensus - Now leader for term 2&lt;BR /&gt;
01-05-2016 19:41:03.431 -0500 INFO SHPRaftConsensus - New commitIndex: 2&lt;BR /&gt;
01-05-2016 19:41:03.431 -0500 INFO SHPoolingMgr - Making node the captain&lt;BR /&gt;
01-05-2016 19:41:03.431 -0500 INFO SHPoolingMgr - makeOrChangeSlave - master_shp = &lt;A href="https://test5421.xx.test.com:8089" target="_blank"&gt;https://test5421.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO SHPRaftConsensus - stepDown(7495)&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO SHPRaftConsensus - Activating configuration 1:\n&amp;lt;configuration&amp;gt;\n&amp;lt;prev_conf&lt;BR /&gt;
iguration&amp;gt;\n&amp;lt;server&amp;gt;\n&amp;lt;server_id&amp;gt;&lt;A href="https://test5421.xx.test.com:8089&amp;lt;/server_id&amp;gt;%5Cn&amp;lt;/server&amp;gt;%5Cn&amp;lt;/prev_configuration&amp;gt;%5Cn&amp;lt;next_configuration&amp;gt;%5Cn&amp;lt;/next_configuration&amp;gt;%5Cn&amp;lt;/configuration&amp;gt;%5Cn" target="_blank"&gt;https://test5421.xx.test.com:8089&amp;amp;lt;/server_id&amp;amp;gt;\n&amp;amp;lt;/server&amp;amp;gt;\n&amp;amp;lt;/prev_configuration&amp;amp;gt;\n&amp;amp;lt;next_configuration&amp;amp;gt;\n&amp;amp;lt;/next_configuration&amp;amp;gt;\n&amp;amp;lt;/configuration&amp;amp;gt;\n&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPRaftConsensus - Exiting and deleting server : &lt;A href="https://test5422.xx.test.com:8089" target="_blank"&gt;https://test5422.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPRaftConsensus - Exiting and deleting server : &lt;A href="https://testa9437.xx.test.com:8089" target="_blank"&gt;https://testa9437.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPRaftConsensus - Exiting and deleting server : &lt;A href="https://test9453.xx.test.com:8089" target="_blank"&gt;https://test9453.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPRaftConsensus - Exiting and deleting server : &lt;A href="https://test9454.xx.test.com:8089" target="_blank"&gt;https://test9454.xx.test.com:8089&lt;/A&gt;&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPoolingMgr - makeOrChangeSlave - master_shp = ?&lt;BR /&gt;
01-05-2016 19:41:03.613 -0500 INFO  SHPRaftConsensus - NOT_LEADER CURRENT_STATE = FOLLOWER&lt;/P&gt;

&lt;P&gt;Note in the above log we see "stepDown(1)"  and "stepDown(7495)"  which does not seems right &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 08:19:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216040#M63364</guid>
      <dc:creator>sat94541</dc:creator>
      <dc:date>2020-09-29T08:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Cluster captain election fails with error -NOT_LEADER CURRENT_STATE = FOLLOWER</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216041#M63365</link>
      <description>&lt;P&gt;when you clear make sure all the nodes are stopped and turn off.&lt;BR /&gt;
Can you try bootstrapping just one member and then keep adding peers using add peer on the captain bootstrapped&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 18:16:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216041#M63365</guid>
      <dc:creator>rbal_splunk</dc:creator>
      <dc:date>2016-01-06T18:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Cluster captain election fails with error -NOT_LEADER CURRENT_STATE = FOLLOWER</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216042#M63366</link>
      <description>&lt;P&gt;Here is what worked::::&lt;/P&gt;

&lt;P&gt;1) Stop all 5 SHC members.&lt;BR /&gt;
2)lean _raft on all nodes &amp;gt; $SPLUNK_HOME/var/run/splunk/_raft. NOTE: It needs to be cleaned from all nodes.&lt;BR /&gt;
3) restart all 5 SHC members&lt;BR /&gt;
6)We initially bootstrapped one member&lt;/P&gt;

&lt;P&gt;Bootstrap one node using command like below and then added peers using add peer on the captain bootstrapped&lt;/P&gt;

&lt;P&gt;splunk bootstrap shcluster-captain -servers_list ":" -auth :&lt;/P&gt;

&lt;P&gt;Here the reference to add peer:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/DistSearch/Addaclustermember#Add_the_instance" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/DistSearch/Addaclustermember#Add_the_instance&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 08:19:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216042#M63366</guid>
      <dc:creator>sat94541</dc:creator>
      <dc:date>2020-09-29T08:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Cluster captain election fails with error -NOT_LEADER CURRENT_STATE = FOLLOWER</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216043#M63367</link>
      <description>&lt;P&gt;It could be network issues leading to the failing in append entries while bootstrapping,--check in splunkd.log&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 18:20:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Head-Cluster-captain-election-fails-with-error-NOT-LEADER/m-p/216043#M63367</guid>
      <dc:creator>rbal_splunk</dc:creator>
      <dc:date>2016-01-06T18:20:30Z</dc:date>
    </item>
  </channel>
</rss>

