@Michael Bronson, You can use these curl calls to run all the service checks and check the status To run service checks curl -ivk -H "X-Requested-By: ambari" -u {ambari-username}:{ambari-password} -X POST -d @payload.txt http://{ambari-server}:{ambari-port}/api/v1/clusters/{cluster-name}/request_schedules Sample response: { "resources": [ { "href": "http://<ambari-server>:8080/api/v1/clusters/<clustername>/request_schedules/68", "RequestSchedule": { "id": 68 // This is the request-schedule-id to be used for second call } } ] } <br> Note: Download the attached payload.txt to some folder and run the above command from the same folder. To get status of service checks curl -ivk -H "X-Requested-By: ambari" -u {ambari-username}:{ambari-password} -X GET http://{ambari-server}:{ambari-port}/api/v1/clusters/{cluster-name}/request_schedules/{request-schedule-id} To get the status of each service, iterate through batch_requests array in the response and look for 'request_status' inside each object. COMPLETED is for passed, FAILED for failed, ABORTED if service check is aborted.payload.txt Note: request-schedule-id for the second curl call is obtained from the response of 1st call. Thanks, Aditya ... View more

I tried this and it returns only the queried table curl -X GET \ 'http://sandbox.hortonworks.com:21000/api/atlas/v2/search/dsl?typeName=hive_table&query=where%20name%3D%22asteroids%22' \ -H 'authorization: Basic YWRtaW46YWRtaW4=' Since the thread was long. I put the correct answer separately. You will find an "Accept" button beside this answer. Please click on it to accept it to make it as Best answer. Thanks a lot. ... View more

@Michael Bronson You can try the following approach to completely remove the unwanted host from your ambari Database. 0. Stop ambari-server. # ambari-server stop 1. Please take a fresh ambari DB dump for safety and backup. 2. Now run the following SQL queries inside your ambari DB to delete the unwanted host. Please replace the "unwanted1.host.com" with your unwanted hostname and similarly the "351" with the "host_id" that you want to remove from your Database. delete from execution_command where task_id in (select task_id from host_role_command where host_id in (351)); delete from host_version where host_id in (351); delete from host_role_command where host_id in (351); delete from serviceconfighosts where host_id in (351); delete from hoststate where host_id in (351); delete from kerberos_principal_host WHERE host_id='unwanted1.host.com'; ----> For kerberized Env delete from hosts where host_name in ('unwanted1.host.com'); delete from alert_current where history_id in ( select alert_id from alert_history where host_name in ('unwanted1.host.com')); 3. Now restart ambari-server. # ambari-server start . ... View more

@Aditya Sirna I found the error... By default "hbase_regionserver_heapsize" was set to 4096m, greater than my server, therefore, regionservers were not able to start. I Changed that value to 1024 and everything went ok! "hbase_regionserver_heapsize" : "4096m", "hbase_regionserver_heapsize" : "1024", ... View more