<?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: Migrate Indexer Cluster to stand alone indexer in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699470#M28597</link>
    <description>&lt;P&gt;I've never done this myself (usually you grow from a stand-alone instance to clustered environment) but there is no real reason why one of your indexers shouldn't work as a stand-alone machine. Of course you know how to remove one indexer from the cluster (I hope you don't have rf=sf=1). If you have rf=2, sf=1 and relatively symmetrical primaries distribution, you might&amp;nbsp; need extra storage since Splunk will have to rebuild index files from raw data on the remaining indexer. If you have rf=sf=2, you'll just get one indexer down and that's it.&lt;/P&gt;&lt;P&gt;One caveat - since your rf/sf will not be met with just one indexer, your cluster will be searchable but not complete since you'll always be missing the other indexer.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2024 22:27:12 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-09-18T22:27:12Z</dc:date>
    <item>
      <title>Migrate Indexer Cluster to stand alone indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699458#M28595</link>
      <description>&lt;P&gt;Hi, we are decomisioning our splunk infra, our company was purchased and the new management want to free resources :(.&lt;/P&gt;&lt;P&gt;We have 3 search heads (stand alone) + 2 indexers (clustered).&lt;/P&gt;&lt;P&gt;They ask me to break the indexer cluster to free storage, cpu and mem, i've found docs about removing nodes but keeping the cluster.&amp;nbsp; We want to keep just one search head (the one with license master) and one indexer.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there documentation to "break" the cluster and keep just one indexer in stand alone mode? (we need to keep info for "auditing reasons").&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know i can just put one in maintenance mode and power off but this procedure is intended to reboot/replace in some time the "faulty" indexer, not to keep it down for ever and ever.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 20:07:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699458#M28595</guid>
      <dc:creator>dieguiariel</dc:creator>
      <dc:date>2024-09-18T20:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate Indexer Cluster to stand alone indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699459#M28596</link>
      <description>&lt;P&gt;A simple way to do it is to remove one indexer from the cluster and run the cluster with a single indexer.&amp;nbsp; You still will need a CM, but you will save storage and 3 servers (2 SH and 1 Idx).&lt;/P&gt;&lt;P&gt;Use the offline command to take down one indexer (maintenance mode not needed) and the CM will ensure all data exists on the remaining indexer (which it should already).&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;splunk offline --enforce-counts&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 18 Sep 2024 20:33:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699459#M28596</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-09-18T20:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate Indexer Cluster to stand alone indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699470#M28597</link>
      <description>&lt;P&gt;I've never done this myself (usually you grow from a stand-alone instance to clustered environment) but there is no real reason why one of your indexers shouldn't work as a stand-alone machine. Of course you know how to remove one indexer from the cluster (I hope you don't have rf=sf=1). If you have rf=2, sf=1 and relatively symmetrical primaries distribution, you might&amp;nbsp; need extra storage since Splunk will have to rebuild index files from raw data on the remaining indexer. If you have rf=sf=2, you'll just get one indexer down and that's it.&lt;/P&gt;&lt;P&gt;One caveat - since your rf/sf will not be met with just one indexer, your cluster will be searchable but not complete since you'll always be missing the other indexer.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 22:27:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699470#M28597</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-09-18T22:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate Indexer Cluster to stand alone indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699582#M28609</link>
      <description>&lt;P&gt;Thank you both for your replies, i was afraid of making a mess keeping a "cluster" with just one node.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have SF and Rf=2, im a aware that probably the searches will trigger a warning about a missing node in the cluster but the searches will be performed only for historical reasons.&lt;/P&gt;&lt;P&gt;Thank you again!&lt;/P&gt;&lt;P&gt;This is a really good community, and Splunk is really an excellent product, im really sad that i had to let this go.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 13:42:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699582#M28609</guid>
      <dc:creator>dieguiariel</dc:creator>
      <dc:date>2024-09-19T13:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate Indexer Cluster to stand alone indexer</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699639#M28610</link>
      <description>&lt;P&gt;Change RF/SF to 1 and the CM will not complain about missing nodes.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 20:04:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Migrate-Indexer-Cluster-to-stand-alone-indexer/m-p/699639#M28610</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-09-19T20:04:56Z</dc:date>
    </item>
  </channel>
</rss>

