Member since
08-08-2017
1652
Posts
30
Kudos Received
11
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1915 | 06-15-2020 05:23 AM | |
| 15444 | 01-30-2020 08:04 PM | |
| 2066 | 07-07-2019 09:06 PM | |
| 8097 | 01-27-2018 10:17 PM | |
| 4565 | 12-31-2017 10:12 PM |
12-21-2017
04:58 PM
No, as long as the agents are already installed you should be good to go.
... View more
12-20-2017
07:33 PM
1 Kudo
@Michael Bronson, HDFS in this cluster is in safemode. Thats why Timelineserver is failing to start. Kindly check HDFS log to see why is Namenode is in safemode. You can explicitly turn off safemode by running "hdfs dfsadmin -safemode leave".
... View more
12-22-2017
03:29 AM
@Michael Bronson Looks like you want to fetch the details of "dfs.datanode.data.dir" property. In that case you can try using the following call. (please revert back if you are talking about a slightly different property) Syntax: # curl -sH "X-Requested-By: ambari" -u admin:admin -X GET "http://$AMBARI_HOSTNAME:8080/api/v1/clusters/$CLUSTER_NAME/configurations/service_config_versions?service_name=HDFS&is_current=true" | grep "\"dfs.datanode.data.dir\"" Example: # curl -sH "X-Requested-By: ambari" -u admin:admin -X GET "http://amb25101.example.com:8080/api/v1/clusters/plain_ambari/configurations/service_config_versions?service_name=HDFS&is_current=true" | grep "\"dfs.datanode.data.dir\"" Output: "dfs.datanode.data.dir" : "/hadoop/hdfs/data", . Please replace the "$AMBARI_HOSTNMAE" and "$CLUSTER_NAME" based on your environment. .
... View more
09-24-2018
06:03 PM
I am having the same problem even after removing the HIVE_SERVER_INTERACTIVE entry in the blueprint . any other suggestions ?
... View more
12-11-2017
03:17 AM
can you see this link: Partioning recomendations
... View more
12-07-2017
06:29 PM
Hi Michael Yes you can use Blueprints 1 - Export blueprints via API call ( GET /api/v1/clusters/:clusterName?format=blueprint ) 2- change the json document 3- Import again the new modified BluePrint json ( POST ... ) For more details about how to use blueprints, please check here
... View more
12-06-2017
01:09 PM
@Michael Bronson Yes, we can change the default ZK port 2181 to something else for all the hosts. That will also be a easily managable option.
... View more
12-06-2017
10:29 AM
@Jay excellent answer ,
... View more
12-05-2017
07:32 PM
@Michael Bronson In your first update the Hostname was not complete for ambari host. (Is that a typo "master02.dddns.com" or it should be "master02" ) curl -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://master02.dddns.com:8080/api/v1/clusters/HDP/hosts/worker04.dddns.com/host_components/METRICS_MONITOR . Also the hostname of worker is different "worker04.dddns.com" (or it should be "worker04.sys45.com") Are you sure that your host "worker04.dddns.com" really has AMS monitor installed to it? Please confirm the same using GET command to see if MONITOR is listed int eh output of the following API call? curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://master02.dddns.com:8080/api/v1/clusters/HDP/hosts/worker04.dddns.com/host_components
... View more
12-05-2017
08:21 PM
1 Kudo
@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