Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Decommission of datanode

avatar

https://cwiki.apache.org/confluence/display/AMBARI...

When the REST API is used to trigger the decommission of the datanode a request ID is returned since its an async operation (see https://github.com/apache/ambari/blob/trunk/ambari...)

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!)

Is this a bug ? Shouldn't the Ambari asynchronous request be marked COMPLETED only after the decommission has finished completely ?

1 ACCEPTED SOLUTION

avatar

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.

View solution in original post

2 REPLIES 2

avatar

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.

avatar

Thanks. It would be helpful to update the cwiki.apache.org URL referred above with information on how to wait for decommission to complete