<?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: Decommission of datanode in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101335#M14041</link>
    <description>&lt;P&gt;The decommission request from does not wait for decommission to complete - it issues the decommission command to hdfs and then hdfs asynchronously continues the decommissioning operation. At this point the jmx data from NN has to be monitored from the outside to know when hdfs completes decommissioning.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jan 2016 11:44:54 GMT</pubDate>
    <dc:creator>smohanty</dc:creator>
    <dc:date>2016-01-05T11:44:54Z</dc:date>
    <item>
      <title>Decommission of datanode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101334#M14040</link>
      <description>&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/display/AMBARI/API+to+decommission+DataNodes+and+NodeManagers"&gt;https://cwiki.apache.org/confluence/display/AMBARI...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When the REST API is used to trigger the decommission of the datanode a request ID is returned since its an async operation (see &lt;A href="https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/index.md#asynchronous-response"&gt;https://github.com/apache/ambari/blob/trunk/ambari...&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/index.md#asynchronous-response"&gt;&lt;/A&gt;After polling on the status of the returned request ID for sometime, the request status shows "COMPLETED". However the decommission is actually still progressing (incomplete!)&lt;/P&gt;&lt;P&gt;Is this a bug ? Shouldn't the Ambari asynchronous request be marked COMPLETED only after the decommission has finished completely ?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2016 11:30:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101334#M14040</guid>
      <dc:creator>krishnanand_tho</dc:creator>
      <dc:date>2016-01-05T11:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Decommission of datanode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101335#M14041</link>
      <description>&lt;P&gt;The decommission request from does not wait for decommission to complete - it issues the decommission command to hdfs and then hdfs asynchronously continues the decommissioning operation. At this point the jmx data from NN has to be monitored from the outside to know when hdfs completes decommissioning.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2016 11:44:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101335#M14041</guid>
      <dc:creator>smohanty</dc:creator>
      <dc:date>2016-01-05T11:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: Decommission of datanode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101336#M14042</link>
      <description>&lt;P&gt;Thanks. It would be helpful to update the cwiki.apache.org URL referred above with information on how to wait for decommission to complete&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2016 12:52:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Decommission-of-datanode/m-p/101336#M14042</guid>
      <dc:creator>krishnanand_tho</dc:creator>
      <dc:date>2016-01-05T12:52:07Z</dc:date>
    </item>
  </channel>
</rss>

