<?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: How does the search header cluster change to a single search header instance? in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429652#M7689</link>
    <description>&lt;P&gt;You need to have as many indexers as you have SF/RF. So if you have SF2/RF2 then you only need two indexers. If you have SF1/RF2 then you need two indexers still. If you have SF1/RF2 and one indexer dies, you won't lose data but you will need to spend time rebuilding the indexes. How long this takes depends on how much data you have.  I hope this helps.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jan 2019 09:58:47 GMT</pubDate>
    <dc:creator>chrisyounger</dc:creator>
    <dc:date>2019-01-29T09:58:47Z</dc:date>
    <item>
      <title>How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429647#M7684</link>
      <description>&lt;P&gt;I have a single site cluster  that  architecture is as follows:&lt;/P&gt;

&lt;P&gt;search header cluster： 4 search head +  a  deployer&lt;BR /&gt;
indexer cluster ：  5 peer node  +  1  master node&lt;/P&gt;

&lt;P&gt;1、I don't want to use search header clustering now. I want to change the architecture to a single search instance . What should I do?&lt;/P&gt;

&lt;P&gt;I want to change to :&lt;/P&gt;

&lt;P&gt;a search head  and no deployer&lt;BR /&gt;
indexer cluster ： 3 peer node  + 1  master node&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/DistSearch/Removeaclustermember"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/DistSearch/Removeaclustermember&lt;/A&gt; &lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Removepeerfrommasterlist"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Removepeerfrommasterlist&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Do I just need to remove 3  cluster members from SHC and  remove 2 peer node from indexer cluster  with reference to the above document? ?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jan 2019 03:39:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429647#M7684</guid>
      <dc:creator>bestSplunker</dc:creator>
      <dc:date>2019-01-28T03:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429648#M7685</link>
      <description>&lt;P&gt;I have been unable to find specific documentation about this scenario, but I think this process should work:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;With all search heads running, make sure the configuration is synced across cluster members (make sure noone is making changes).&lt;/LI&gt;
&lt;LI&gt;Stop all search heads and search head deployer.&lt;/LI&gt;
&lt;LI&gt;On the box you want to use as a standalone, edit &lt;CODE&gt;etc/system/local/server.conf&lt;/CODE&gt; and comment out the &lt;CODE&gt;[shclustering]&lt;/CODE&gt; section and &lt;CODE&gt;[replication_port:..&lt;/CODE&gt; sections.&lt;/LI&gt;
&lt;LI&gt;Start splunk on the solo box. Don't ever turn on the other boxes again. &lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Yes you can convert to a single indexer if you have enough storage space. You can use the instructions here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Takeapeeroffline#Take_a_peer_down_permanently:_the_enforce-counts_offline_command"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/Indexer/Takeapeeroffline#Take_a_peer_down_permanently:_the_enforce-counts_offline_command&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jan 2019 04:15:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429648#M7685</guid>
      <dc:creator>chrisyounger</dc:creator>
      <dc:date>2019-01-28T04:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429649#M7686</link>
      <description>&lt;P&gt;The last question , can I convert an indexer cluster to an indexer? At present, the search factor is 2 and the replication factor is 3, which means that the indexer keeps two searchable copies. If I remove multiple peers from the indexer, if I guarantee that an indexer's data is complete?How can I do this without loss and repetition?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jan 2019 14:06:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429649#M7686</guid>
      <dc:creator>bestSplunker</dc:creator>
      <dc:date>2019-01-28T14:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429650#M7687</link>
      <description>&lt;P&gt;Hi,   You cannot have a SF or RF of more than 1 if you only have one indexer.  You would need to keep at least 3 indexers. Otherwise reduce your SF/RF first.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jan 2019 19:28:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429650#M7687</guid>
      <dc:creator>chrisyounger</dc:creator>
      <dc:date>2019-01-28T19:28:23Z</dc:date>
    </item>
    <item>
      <title>Re: How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429651#M7688</link>
      <description>&lt;P&gt;@chrisyoungerjds  thank you for your reply. now ,I want to convert to 1 search head + indexer cluster with 3 peer nodes+1 master node. According to the above method, can I really do it? Now replication factor 3, the search factor is 2. If I convert, should the replication factor be changed to 2 and the search factor changed to 1?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 09:52:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429651#M7688</guid>
      <dc:creator>bestSplunker</dc:creator>
      <dc:date>2019-01-29T09:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: How does the search header cluster change to a single search header instance?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429652#M7689</link>
      <description>&lt;P&gt;You need to have as many indexers as you have SF/RF. So if you have SF2/RF2 then you only need two indexers. If you have SF1/RF2 then you need two indexers still. If you have SF1/RF2 and one indexer dies, you won't lose data but you will need to spend time rebuilding the indexes. How long this takes depends on how much data you have.  I hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 09:58:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/How-does-the-search-header-cluster-change-to-a-single-search/m-p/429652#M7689</guid>
      <dc:creator>chrisyounger</dc:creator>
      <dc:date>2019-01-29T09:58:47Z</dc:date>
    </item>
  </channel>
</rss>

