Member since
08-08-2017
1652
Posts
30
Kudos Received
11
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1996 | 06-15-2020 05:23 AM | |
| 16401 | 01-30-2020 08:04 PM | |
| 2144 | 07-07-2019 09:06 PM | |
| 8333 | 01-27-2018 10:17 PM | |
| 4722 | 12-31-2017 10:12 PM |
09-11-2017
06:51 PM
@uri ben-ari That error you will get only when you have not specified the "Cluster Name" aftaer the ambari server hostname in the config.sh command: /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 get amb25101.example.com plain_ambari cluster-env /tmp/cluster-env.txt .
... View more
09-06-2017
11:23 PM
5 Kudos
@uri ben-ari Please try the curl command with double quotes (escaping the double quotes needed as part of curl rrequest) curl -H "X-Requested-By: ambari" -u admin:admin -X PUT -d "{\"RequestInfo\":{\"query\":\"ServiceComponentInfo/component_name.in(${LIST})\"},\"ServiceComponentInfo\":{\"recovery_enabled\":\"true\"}}" http://localhost:8080/api/v1/clusters/HDP01/components?
... View more
09-04-2017
04:48 PM
another note the components - JournalNode,ZKFailoverController are still disable
... View more
09-01-2017
07:01 PM
Here you have no problem in the log. It's only a warning. And this is because you have another Spark application running and then the port 4040 (which is the default port for the Spark Monitoring UI) is already in use. But then it will try on port 4041 and so on, until it finds a free port, as you can see in the following log, The only problem I can see is that you are specifying an invalid port number (100015 is not a valid port number, I guess you meant 10015).
... View more
08-29-2017
10:14 AM
generic question , do we need to do restart after each parameter settings ? or we can do after we set all parameters?
... View more
08-30-2017
06:18 AM
1 Kudo
you can restart after you set all parameters. but might be difficult to troubleshoot if some of the services fail to start.
... View more
08-29-2017
05:29 AM
@uri ben-ari To list all the requests use the following API and see what is the maximum request ID (which will be the recent one, Higher the requestID more recent one it is): # curl -sH "X-Requested-By: ambari" -u admin:admin -i http://localhost:8080/api/v1/clusters/Sandbox/requests?fields=Requests/request_status | grep -A 1 id | awk '{print $NF}' > /tmp/requests_details.txt; sed -e '1,2d' -e s'/--//g' -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/requests_details.txt | awk 'NR%2{printf "%s ",$0;next;}1' Example Output: 185, COMPLETED
186, COMPLETED
187, COMPLETED
188, FAILED
189, COMPLETED
190, COMPLETED
191, COMPLETED
193, COMPLETED
195, COMPLETED
196, COMPLETED
197, COMPLETED
198, COMPLETED
199, COMPLETED
200, COMPLETED
201, COMPLETED
202, COMPLETED
203, COMPLETED
204, COMPLETED
206, ABORTED . . Then if you want to see only the IN_PROGRESS requests then you can make the following API call. # curl -sH "X-Requested-By: ambari" -u admin:admin -i http://localhost:8080/api/v1/clusters/Sandbox/requests?fields=Requests/request_status | grep -A 1 id | awk '{print $NF}' > /tmp/requests_details.txt; sed -e '1,2d' -e s'/--//g' -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/requests_details.txt | awk 'NR%2{printf "%s ",$0;next;}1' | grep -i 'IN_PROGRESS' Example Output: # curl -sH "X-Requested-By: ambari" -u admin:admin -i http://localhost:8080/api/v1/clusters/Sandbox/requests?fields=Requests/request_status | grep -A 1 id | awk '{print $NF}' > /tmp/requests_details.txt; sed -e '1,2d' -e s'/--//g' -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/requests_details.txt | awk 'NR%2{printf "%s ",$0;next;}1' | grep -i 'IN_PROGRESS'
207, IN_PROGRESS
.
... View more
08-28-2017
06:08 AM
@uri ben-ari Please try something like following: # curl -sH "X-Requested-By: ambari" -u admin:admin -i http://localhost:8080/api/v1/hosts?fields=Hosts/host_name,Hosts/ip | grep -A 1 host_name | awk '{print $NF}' > /tmp/hosts_details.txt; sed -e '1,2d' -e s'/--//g' -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/hosts_details.txt | awk 'NR%2{printf "%s ",$0;next;}1 . Example Output: # curl -sH "X-Requested-By: ambari" -u admin:admin -i http://amb25101.example.com:8080/api/v1/hosts?fields=Hosts/host_name,Hosts/ip | grep -A 1 host_name | awk '{print $NF}' > /tmp/hosts_details.txt; sed -e '1,2d' -e s'/--//g' -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/hosts_details.txt | awk 'NR%2{printf "%s ",$0;next;}1'
amb25101.example.com 172.10.116.149
amb25102.example.com 172.10.116.148
amb25103.example.com 172.10.116.151
amb25104.example.com 172.10.116.150 .
... View more
08-27-2017
11:09 AM
@uri ben-ari Following should list all the components that has stale config, and need to be restaretd to get the config changes reflected. # curl -i --user admin:admin -i -H 'X-Requested-By: ambari' -X GET http://localhost:8080/api/v1/clusters/Sandbox/host_components?HostRoles/stale_configs=true
Here please replace the following: 1. "localhost" : with the Ambari FQDN 2. 8080 : with ambari port. 3. Sandbox : With cluster Name .
... View more
08-23-2017
05:03 AM
@uri ben-ari The error indicates that you are not passing the correct "zookeeper.connect" property value to the flag "--zookeeper" in the command line. You can get the "zookeeper.connect" value from Ambari UI --> Kafka --> Configs --> Kafka Broker --> "zookeeper.connect" In my case the value was : "amb25103.example.com:2181,amb25102.example.com:2181,amb25101.example.com:2181" So i had to use the following command: Example: # /usr/hdp/2.6.0.3-8/kafka/bin/kafka-preferred-replica-election.sh --zookeeper amb25103.example.com:2181,amb25102.example.com:2181,amb25101.example.com:2181 .
... View more