Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2712 | 04-27-2020 03:48 AM | |
| 5271 | 04-26-2020 06:18 PM | |
| 4440 | 04-26-2020 06:05 PM | |
| 3565 | 04-13-2020 08:53 PM | |
| 5367 | 03-31-2020 02:10 AM |
05-10-2017
03:44 AM
@sivareddy akkala - It is really not a good idea to delete a service once the Upgrade is started. As it might create DB corruption and pending item in the scheduled upgrade tasks items/upgrade groups. - Is there any specific reason you deleted that service? - Also which kind of upgrade are you performing? (Rolling or Express Upgrade)? - Have you run the pre-upgrade service checks (Ambari usually asks when we start performing upgrade) ? - Can you also share the output of the following URLs? http://<ambari_server>:8080/api/v1/clusters/<cluster_name>/upgrades In the above URL whatever is the latest <upgrade_id> take that value and form the following kind of URL and then share that output as well: http://<ambari_server>:8080/api/v1/clusters/<cluster_name>/upgrades/<upgrade_id>?fields=upgrade_groups/upgrade_items/tasks/Tasks/status,upgrade_groups/upgrade_items/tasks/Tasks/command_detail,upgrade_groups/upgrade_items/tasks/Tasks/stderr,upgrade_groups/upgrade_items/tasks/Tasks/host_name .
... View more
05-10-2017
12:38 AM
@sivareddy akkala Please check the Falcon logs because it is 503 (Internal Server Error), means Falcon is having some internal server issues. Check in the logs if you find any ERROR and please share the same. Also please check the following directory permissions and ownership is correct? [root@sandbox ~]# ls -ld /hadoop
drwxr-xr-x 10 root root 110 Apr 6 07:16 /hadoop
[root@sandbox ~]# ls -ld /hadoop/falcon/
drwxr-xr-x 5 falcon root 46 Sep 15 2016 /hadoop/falcon/
[root@sandbox ~]# ls -ld /hadoop/falcon/data
drwxr-xr-x 3 root root 20 Sep 15 2016 /hadoop/falcon/data
[root@sandbox ~]# ls -ld /hadoop/falcon/data/lineage/
drwxrwxr-x 3 falcon hadoop 20 Sep 15 2016 /hadoop/falcon/data/lineage/
[root@sandbox ~]# ls -ld /hadoop/falcon/data/lineage/graphdb/
drwxrwxr-x 2 falcon hadoop 54 Sep 15 2016 /hadoop/falcon/data/lineage/graphdb/
[root@sandbox ~]# ll /hadoop/falcon/data/lineage/graphdb/je.lck
-rw-r--r-- 1 falcon hadoop 0 Sep 13 2016 /hadoop/falcon/data/lineage/graphdb/je.lck .
... View more
05-09-2017
06:12 PM
@Theyaa Matti
Currently i do not have Ambari 2.1 setup ready to test the same .... but i guess it should be working as expected or else it might be enhanced to show the service name in later version of ambari 2.1
... View more
05-09-2017
06:10 PM
@Theyaa Matti
Which ambari version are you using? Also can you please share the exact command and response output here?
I just now tried the same on Ambaei 2.4.0.0 and can se this thing working fine.
http://localhost:8080/api/v1/clusters/Sandbox/host_components?HostRoles/stale_configs=true&fields=HostRoles/service_name
.
... View more
05-09-2017
05:16 PM
@sivareddy akkala Please login to Amabri UI and navigate to: Ambari UI -> Hive -> Configs -> Filter, check jars listed in property "templeton.libjars" And then change the value as following then restart the services that needs required restart in the ambari UI. templeton.libjars= /usr/hdp/${hdp.version}/zookeeper/zookeeper.jar,/usr/hdp/${hdp.version}/hive/lib/hive-common.jar . You can also find the HCC article on similar line: https://community.hortonworks.com/articles/15958/templetonlibjars-property-changed-its-value-after.html
... View more
05-09-2017
05:14 PM
@sivareddy akkala
What i meant in my previous comment is that ... you were supposed to click the "Accept" button for the update that resolved the issue (or answered your query). Here you accepted your own update which does not have the answer.
... View more
05-09-2017
04:39 PM
@sivareddy akkala
Good to know that it was useful. It will be great if you can click on the "Accept" link on this thread
and mark this thread as "Answered", that will be useful for other users
as well.
... View more
05-09-2017
03:37 PM
@Bharadwaj Bhimavarapu Good to know that the detail was useful. It will be great if you can click on the "Accept" link on this thread and mark this thread as "Answered", that will be useful for other users as well.
... View more
05-09-2017
05:16 AM
@Bharadwaj Bhimavarapu Based on the thread title you want to know how to get components status (running,stopped) from ambari REST API's? However later you mentioned that "you want to read Ambari alerts through NIFI using REST API's", Can you please clarify which alert are you getting and Are you sure that you want to read the component status from Alerts? - If you simply want to read the component status (like NIFI) then you can make the following kind of REST Curl call:
curl -u admin:admin -H "X-Requested-By:ambari" -i -X GET http://localhost:8080/api/v1/clusters/Sandbox/hosts/sandbox.hortonworks.com/host_components/NIFI_MASTER . OR more precisely
curl -u admin:admin -H "X-Requested-By:ambari" -i -X GET http://localhost:8080/api/v1/clusters/Sandbox/hosts/sandbox.hortonworks.com/host_components/NIFI_MASTER?fields=HostRoles/component_name,HostRoles/host_name,HostRoles/state,HostRoles/service_name Example output will be something like: .
... View more
05-09-2017
04:54 AM
@sivareddy akkala Looks like you are using ambari 2.4 or prior version. From ambari 2.5 this bug has been fixed: https://issues.apache.org/jira/browse/AMBARI-18536 . Explanation Of this error:
That particular curl command is trying to send the request as if it was an HTML form post, using "Content-Type: application/x-www-form-urlencoded". That causes the jetty server to try to slurp the whole request into memory and try to parse the key-value pairs of an HTML form out of it.
So as part of that fix the command is slightly changed as [1] so that it will not treat the request like an HTML form post and instead uses "Content-Type: application/octet-stream". . [1] "Code Change Detail" .
... View more