<?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>question Re: Need suggestion to stop or Decommission Datanode? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239077#M200888</link>
    <description>&lt;P&gt;&lt;A rel="noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer" href="http://madhura%20mhatre/" target="_blank"&gt;&lt;EM&gt;@Madhura Mhatre&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt; &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Surely you could just t^do that but what happens to the replicas stored on that particular data node? Somehow your cluster has to reconstruct those replicas if you had a replicator factor of more than 1. &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Here I was talking about planned maintenance! Just switching it off will also force your cluster to do the same thing in the background with alerts and ONLY when the replicas have been reconstructed will those alerts go away.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;There is a performance cost for both decommissioning and just unplugging the data node.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Apr 2019 11:38:22 GMT</pubDate>
    <dc:creator>Shelton</dc:creator>
    <dc:date>2019-04-25T11:38:22Z</dc:date>
    <item>
      <title>Need suggestion to stop or Decommission Datanode?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239074#M200885</link>
      <description>&lt;P&gt;Hi , We are using 12 Datanodes in our cluster. And we have 3 replication factor. &lt;/P&gt;&lt;P&gt;Currently we are doing cost optimization and our total cluster is 35% used. We want to remove one datanode from our cluster, but we want to see first how our cluster performs on 11 datanodes. if it doesn't perform well, we need to restart that datanode again.&lt;/P&gt;&lt;P&gt;To experiment this- Do I need to Stop the datanode or Decomission datanode?&lt;/P&gt;&lt;P&gt;Please need suggestion.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 22:55:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239074#M200885</guid>
      <dc:creator>madhura2688</dc:creator>
      <dc:date>2019-04-24T22:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Need suggestion to stop or Decommission Datanode?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239075#M200886</link>
      <description>&lt;P&gt;&lt;A rel="noopener noreferrer noopener noreferrer nofollow noopener noreferrer" href="http://@Madhura%20Mhatre" target="_blank"&gt;@Madhura Mhatre&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; It's well documented in by &lt;/EM&gt;&lt;A rel="noopener noreferrer noopener noreferrer nofollow noopener noreferrer" href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/managing-and-monitoring-ambari/content/amb_decommission_a_datanode.html" target="_blank"&gt;&lt;EM&gt;hortonworks&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt;  Once you launch the decommissioning the blocks on that node  will be distributed to the other node remaining nodes&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="108134-decom-datanode.png" style="width: 901px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/14006iC6CCFDDE994BB440/image-size/medium?v=v2&amp;amp;px=400" role="button" title="108134-decom-datanode.png" alt="108134-decom-datanode.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;If the replication factor is higher than the number of existing data nodes after the removal, the removal process is not going to succeed!&lt;/STRONG&gt; &lt;/P&gt;</description>
      <pubDate>Sat, 17 Aug 2019 22:47:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239075#M200886</guid>
      <dc:creator>Shelton</dc:creator>
      <dc:date>2019-08-17T22:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: Need suggestion to stop or Decommission Datanode?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239076#M200887</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1271/sheltong.html"&gt;@Geoffrey Shelton Okot&lt;/A&gt; Thank you for your response. Instead of Decommissioning the node Can I stop it?&lt;/P&gt;&lt;P&gt;What is the difference? Whats the best way to stop it or Decommission?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 09:48:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239076#M200887</guid>
      <dc:creator>madhura2688</dc:creator>
      <dc:date>2019-04-25T09:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: Need suggestion to stop or Decommission Datanode?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239077#M200888</link>
      <description>&lt;P&gt;&lt;A rel="noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer" href="http://madhura%20mhatre/" target="_blank"&gt;&lt;EM&gt;@Madhura Mhatre&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt; &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Surely you could just t^do that but what happens to the replicas stored on that particular data node? Somehow your cluster has to reconstruct those replicas if you had a replicator factor of more than 1. &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Here I was talking about planned maintenance! Just switching it off will also force your cluster to do the same thing in the background with alerts and ONLY when the replicas have been reconstructed will those alerts go away.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;There is a performance cost for both decommissioning and just unplugging the data node.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 11:38:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239077#M200888</guid>
      <dc:creator>Shelton</dc:creator>
      <dc:date>2019-04-25T11:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: Need suggestion to stop or Decommission Datanode?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239078#M200889</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1271/sheltong.html" nodeid="1271"&gt;@Geoffrey Shelton Okot&lt;/A&gt; Thank you. I think Decommissioning is a best way to do this. Do I need to turn on maintainance mode while I do decommissioning datanode? Also Do I need to stop the services like - NodeManager, Ambari metrics for that datanode after decommissioning? &lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 08:26:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Need-suggestion-to-stop-or-Decommission-Datanode/m-p/239078#M200889</guid>
      <dc:creator>madhura2688</dc:creator>
      <dc:date>2019-04-26T08:26:20Z</dc:date>
    </item>
  </channel>
</rss>

