The JSON in the payload is incorrect: {"RequestInfo":{"context":"Stop DATANODE"},"Body":"HostRoles":{"state":"INSTALLED"}} Should be: {"RequestInfo":{"context":"Stop DATANODE"},"Body":{"HostRoles":{"state":"INSTALLED"}}} Note the added set of { and } around the HostRoles data. ... View more

In ambari version AMBARI-2.5.1.7 we needed to do another step after recommissioning steps above mentioned. The nodemanger was going to stopped state after the recommissioning call. Needed to change the state from installed to started. curl -u user:pass -i -H 'X-Requested-By: ambari' -X PUT -d '{"HostRoles": {"state": "STARTED"}}' http://{$ambari_master_host}:{$ambari_master_port}/api/v1/clusters/{$clustername}hosts/{$host}/host_components/NODEMANAGER; Same steps are followed by the ambari server when doing the recommission. PFA the logs // Recomission ( Decommission with include host ) 14 Feb 2018 13:28:23,479 INFO [ambari-client-thread-75749] AmbariManagementControllerImpl:3984 - Received action execution request, clusterName=xxxx , request=isCommand :true, action :null, command :DECOMMISSION, inputs :{included_hosts=xxxx, slave_type=NODEMANAGER}, resourceFilters: [RequestResourceFilter{serviceName='YARN', componentName='RESOURCEMANAGER', hostNames=[]}], exclusive: false, clusterName :xxxx 14 Feb 2018 13:28:23,488 INFO [ambari-client-thread-75749] AmbariCustomCommandExecutionHelper:967 - Recommissioning NODEMANAGER and marking Maintenance=OFF on xxx 14 Feb 2018 13:28:32,906 INFO [qtp-ambari-agent-75726] HeartBeatHandler:332 - HeartBeatHandler.sendCommands: sending ExecutionCommand for host xxx role RESOURCEMANAGER, roleCommand CUSTOM_COMMAND, and command ID 25366-0, task ID 45097 // Ambari changes state from Started to Installed 14 Feb 2018 13:28:44,295 INFO [ambari-heartbeat-processor-0] HeartbeatProcessor:609 - State of service component NODEMANAGER of service YARN of cluster xxx has changed from STARTED to INSTALLED at host xxxx according to STATUS_COMMAND report 14 Feb 2018 13:30:29,889 INFO [ambari-client-thread-75692] AbstractResourceProvider:939 - Received a updateHostComponent request, clusterName=xxx , serviceName=YARN, componentName=NODEMANAGER, hostname=xxxxx request={ clusterName=xxxx , serviceName=YARN, componentName=NODEMANAGER, hostname= xxxx , publicHostname=null, desiredState=STARTED, state=null, desiredStackId=null, staleConfig=null, adminState=null, maintenanceState=null} // Ambari changes state again from Started to Installed 14 Feb 2018 13:30:29,890 INFO [ambari-client-thread-75692] AbstractResourceProvider:650 - Handling update to host component, clusterName=xxx, serviceName=YARN, componentName=NODEMANAGER, hostname=xxxxx , currentState=INSTALLED, newDesiredState=STARTED 14 Feb 2018 13:30:29,910 INFO [ambari-action-scheduler] ServiceComponentHostImpl:1028 - Host role transitioned to a new state, serviceComponentName=NODEMANAGER, hostName=xxxx oldState=INSTALLED, currentState=STARTING ... View more

Mobaxterm, pdsh, ansible, chef, saltstack any of these tools can execute in parallel across your nodes. ... View more

Hi all, I am wondering if there is a reliable way to tell the completion of a NodeManager decommission? For the DataNode decommission, I can do so by checking NameNode's log for completion. But it seems that there is no clear message from ResourceManager's log. Cheers, ... View more

@Ram D I think Terry answered it best. ... View more

@Ram D ah ok, yes in this example you will get FQDN of the server name for URL. I didn't know you can do that in curl command but basically if you run hostname -f as Linux command, you will get FQDN of your host. In context of the curl command, it will populate the URL programmatically with FQDN instead of using the node name explicitly. ... View more

Steps to update OS patches. 1) Stop all application on cluster 2) Apply the OS patches. 3) Reboot the system if required. 4) start all application on cluster 5) Validate all services. ... View more

Can you please provide the links for disaster recovery of ambari-server ? ... View more

@Ram D, See this http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_Ambari_Users_Guide/content/_how_to_configure_namenode_high_availability.html Amabri 2.1.0 but its not different from 2.2. - You can use this too for NN and RM + more http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.0.0/bk_Ambari_Users_Guide/content/ch_managing_service_high_availability.html ... View more

@Paula Morais I got the solution for this. After decommissioning the node, first you need to check /etc/hosts file whether decommissioned host is present or not on Name node host. I am sure, it will be there, try to delete that decommissioned host name and restart Namenodes, later check /etc/hosts file. You need to restart the HDFS and Mapreduce i believe, anyway it will show you on ambari dash board which services need to be restarted. Thank you and let me know it is worked for you or not. It worked for me. ... View more