<?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: Question About Splunk Search Header Captain Selection in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Can-someone-explain-the-majority-principle-of-search-header/m-p/628849#M26616</link>
    <description>&lt;P&gt;1) SHC members are called "members" or "nodes", but not "generations".&amp;nbsp; A generation refers to the set of primary buckets that will be searched.&lt;/P&gt;&lt;P&gt;The number of members needed for a SHC majority is set when the cluster is defined.&amp;nbsp; For a 5-member cluster that number will always be 3, regardless of how many are up or down.&lt;/P&gt;&lt;P&gt;2) Three is the minimum to ensure an election is possible if a member is unavailable.&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 15:11:26 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-01-30T15:11:26Z</dc:date>
    <item>
      <title>Can someone explain the majority principle of search header clustering captain election?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-someone-explain-the-majority-principle-of-search-header/m-p/628828#M26613</link>
      <description>&lt;P&gt;I have a question because I am confused about the majority principle of search header clustering captain election.&lt;/P&gt;
&lt;P&gt;the question is&lt;BR /&gt;Assume a dynamic Captain Election.&lt;/P&gt;
&lt;P&gt;[1]&lt;BR /&gt;When conducting Captain Election, a majority of the cluster members must vote to be elected.&lt;/P&gt;
&lt;P&gt;In step 1, more than half means&lt;/P&gt;
&lt;P&gt;For example, if there are 5 search headers and one is in the Down state,&lt;/P&gt;
&lt;P&gt;I am confused whether the 3rd generation, which is the majority of the 4th generation, should vote, or whether the 3rd generation, which is the majority of the 5th generation, should vote.&lt;/P&gt;
&lt;P&gt;In other words, I wonder if it is included even if the target of the vote is down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[2]&lt;BR /&gt;Also, according to the majority rule, there must be at least three Search Header. I don't know why Search Header needs to be 3 generations.&lt;/P&gt;
&lt;P&gt;For example, if there are only two A and B, here B declares to be the captain first, then A votes and B votes for himself, so more than half of the votes are satisfied, so B can become the captain is not it?&lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2023 16:40:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-someone-explain-the-majority-principle-of-search-header/m-p/628828#M26613</guid>
      <dc:creator>munang</dc:creator>
      <dc:date>2023-02-01T16:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: Question About Splunk Search Header Captain Selection</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-someone-explain-the-majority-principle-of-search-header/m-p/628849#M26616</link>
      <description>&lt;P&gt;1) SHC members are called "members" or "nodes", but not "generations".&amp;nbsp; A generation refers to the set of primary buckets that will be searched.&lt;/P&gt;&lt;P&gt;The number of members needed for a SHC majority is set when the cluster is defined.&amp;nbsp; For a 5-member cluster that number will always be 3, regardless of how many are up or down.&lt;/P&gt;&lt;P&gt;2) Three is the minimum to ensure an election is possible if a member is unavailable.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 15:11:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-someone-explain-the-majority-principle-of-search-header/m-p/628849#M26616</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-30T15:11:26Z</dc:date>
    </item>
  </channel>
</rss>

