@Michael Bronson There are a different possible reasons why the install failed. Will list out a couple of them here 1. Invalid configs in topology/ Invalid topology: In this scenario, your Ambari background operations will show Logical request in Pending status. Ambari-server.log will have the info about which configuration had invalid values 2. Service install/start failures: Details of failures will be available in Ambari background operations window. You can also use Ambari API to figure out what failed. And individual service logs usually have more details about the failure. E.g http://<AMBARI_HOST>:8080/api/v1/clusters/cl1/requests?to=end&page_size=100&fields=tasks/*&tasks/Tasks/status=FAILED Hope this helps! ... View more

@Michael Bronson curl -u {ambari_username}:{ambari_password} -H "X-Requested-By:ambari" -i GET http://localhost:8080/api/v1/clusters/cl1/components?fields=ServiceComponentInfo/state ... View more

@Michael Bronson You can get the service components status from the "ServiceComponentInfo/state" parameter. 1. To get all components state in single API: API : <AMBARI_HOST>/api/v1/clusters/cl1/components?fields=ServiceComponentInfo/state E.g In the response you can find something like this when MR History server is stopped: "ServiceComponentInfo": {"cluster_name": "cl1","component_name": "HISTORYSERVER","service_name": "MAPREDUCE2","state": "INSTALLED"} 2. To get more info for individual component, You can use this API resource <AMBARI_HOST>/api/v1/clusters/cl1/services/MAPREDUCE2/components/HISTORYSERVER Hopefully this helps! ... View more

@Alluri Krishna Raju, Could you please post the failure logs from the ambari background operations window or log files for the start failures? ... View more

@Naseem Could you please post the logs of the Ranger admin start process from the Ambari background operations window? ... View more

@samarth srivastava Just in case if you're looking for the API to restart required services after some configuration chnages, You can use a GET call to find out the components to be restarted. http://${AMBARI_HOST}:8080/api/v1/clusters/${CLUSTER_NAME}/host_components?HostRoles/stale_configs=true And if a list of components to be restarted is returned, you can invoke a POST request with a request body as below: http://${AMBARI_HOST}:8080/api/v1/clusters/${CLUSTER_NAME}/requests Request body: { "RequestInfo": { "command": "RESTART", "context": "Restart all required services", "operation_level": "host_component" }, "Requests/resource_filters": [{ "hosts_predicate": "HostRoles/stale_configs=true" }] } Note: This API works with Ambari version 2.4+ only. ... View more