@Jay , after we do the decommission on some datanode , do we need also to stop the components on that datanode ? and then replaced the disk , or maybe it is inoufgh to decomission without to stop the componet and then replaced the disk ?
... View more
what we get is only that curl -u admin:admin -H "X-Requested-By: ambari" -X GET "http://name2:8080/api/v1/clusters/clu45/host_components?HostRoles/component_name=NAMENODE&metrics/dfs/FSNamesytem/HAState=standby"
{
"href" : "http://name2:8080/api/v1/clusters/clu45/host_components?HostRoles/component_name=NAMENODE&metrics/dfs/FSNamesystem/HAState=standby",
"items" : [ ]
... View more
hi all we want to verify the name nodes status from ambari by API ( namenode adtive/stand by under hdfs ) capture.png is it possible to create API for that?
... View more
@Jay , now its clear, thanks to your great explain , when I do decommission , is it mean that datanode component can be up? , of before the decommision we need to stop anyway the componet on the datanode ?
... View more
@Jay , but it will Decommission all datanode ? , and we want to Decommission only the datanode with the faulty disk ( am I right here ? ) , or some other option to Decommission only the specific datanode ( worker03 )
... View more
we have ambari cluster with 176 datanodes machines ( workers ) each datanode have the following component: capture.png DataNode / HDFS
Metrics Monitor / Ambari Metrics
NodeManager / YARN
how to restart all these component on all datanode machines by API * because it will take time to restart all datanode component manual as ( access each datanode machine from ambari and perform --> host actions --> restart all )
... View more
