<?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: What is the process of decommissioning indexers? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499776#M85179</link>
    <description>&lt;P&gt;Add your new indexers, then update your forwarders to send data to the new indexers (not the old ones)&lt;BR /&gt;
This will prevent the disk space on the old indexers causing the forwarding queues to fill up.&lt;/P&gt;

&lt;P&gt;Your first decomissioned idx will have to transfer (ideally) primacy of approx 33% of buckets, and once that is done, the cluster will replicate buckets to the remaining 5 indexers. &lt;BR /&gt;
With 6TB volumes, this is likely to take several hours (possibly days depending on spec etc).&lt;/P&gt;

&lt;P&gt;Note - you could start by doing a data rebalance which will split the data equally between the old and new peers - whilst this would speed up each old decom, it is a very lengthy process, and would probably take longer than just running the decom process.&lt;BR /&gt;
By the time you have decomissioned all 3 old indexers, you data should be reasonably well balanced across the new servers.&lt;/P&gt;</description>
    <pubDate>Fri, 31 Jan 2020 19:41:39 GMT</pubDate>
    <dc:creator>nickhills</dc:creator>
    <dc:date>2020-01-31T19:41:39Z</dc:date>
    <item>
      <title>What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499773#M85176</link>
      <description>&lt;P&gt;When you run the offline command permanently on an indexer.&lt;/P&gt;

&lt;P&gt;1) How much time does it take to reassign the data to other members in cluster&lt;BR /&gt;
2)Can we run offline command on three indexers at a time or do we need to wait for anything?&lt;BR /&gt;
3) Adding and removing members is correct order or the other way around?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 17:54:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499773#M85176</guid>
      <dc:creator>vrmandadi</dc:creator>
      <dc:date>2020-01-31T17:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499774#M85177</link>
      <description>&lt;P&gt;1.) It depends - how much data your indexer hold primary copies for, network/disk IO, cpu load etc. (It can take some time)&lt;BR /&gt;
2.) No - Dont do this, decom one indexer at a time.&lt;BR /&gt;
3.) Add new indexers first - more indexers in your cluster will speed up the decom process for the old ones, and will begin balancing buckets to the new peers as soon as the process starts. &lt;BR /&gt;
Once you have added all your new indexers, remove the old ones one at a time.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 17:58:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499774#M85177</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2020-01-31T17:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499775#M85178</link>
      <description>&lt;P&gt;when you say some time like 6TB storage ,does it take days? or hours.We have a lot of issues with disk space space falling below 5000MB and thus the indexer stopped accepting new data.This made the HF queues getting filled.All of sudden the data  burts in , data delay ...Does this cause data loss even if other Indexers are running?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 18:45:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499775#M85178</guid>
      <dc:creator>vrmandadi</dc:creator>
      <dc:date>2020-01-31T18:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499776#M85179</link>
      <description>&lt;P&gt;Add your new indexers, then update your forwarders to send data to the new indexers (not the old ones)&lt;BR /&gt;
This will prevent the disk space on the old indexers causing the forwarding queues to fill up.&lt;/P&gt;

&lt;P&gt;Your first decomissioned idx will have to transfer (ideally) primacy of approx 33% of buckets, and once that is done, the cluster will replicate buckets to the remaining 5 indexers. &lt;BR /&gt;
With 6TB volumes, this is likely to take several hours (possibly days depending on spec etc).&lt;/P&gt;

&lt;P&gt;Note - you could start by doing a data rebalance which will split the data equally between the old and new peers - whilst this would speed up each old decom, it is a very lengthy process, and would probably take longer than just running the decom process.&lt;BR /&gt;
By the time you have decomissioned all 3 old indexers, you data should be reasonably well balanced across the new servers.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 19:41:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499776#M85179</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2020-01-31T19:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499777#M85180</link>
      <description>&lt;P&gt;Thank you &lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 21:21:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499777#M85180</guid>
      <dc:creator>vrmandadi</dc:creator>
      <dc:date>2020-01-31T21:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: What is the process of decommissioning indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499778#M85181</link>
      <description>&lt;P&gt;@nickhillscpl  how do we know that that a indexer which is decommissioning  has transferred all its data to the other cluster members&lt;/P&gt;</description>
      <pubDate>Sat, 01 Feb 2020 02:18:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-process-of-decommissioning-indexers/m-p/499778#M85181</guid>
      <dc:creator>vrmandadi</dc:creator>
      <dc:date>2020-02-01T02:18:54Z</dc:date>
    </item>
  </channel>
</rss>

