Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2729 | 04-27-2020 03:48 AM | |
| 5287 | 04-26-2020 06:18 PM | |
| 4457 | 04-26-2020 06:05 PM | |
| 3583 | 04-13-2020 08:53 PM | |
| 5383 | 03-31-2020 02:10 AM |
03-20-2018
10:54 AM
@Michael Bronson Inside ambari DB you can find the following entry to see your VDF
# SELECT version_xml FROM repo_version; .
... View more
03-20-2018
10:25 AM
@Michael Bronson As the error says invalid VDF so it is better to check if there is any issue with the VDF before proceeding with the upgrade. Unable to run upgrade checks because of an invalid VDF .
... View more
03-20-2018
10:05 AM
1 Kudo
@Michael Bronson Something like this you can try: # curl -u admin:admin -H 'X-Requested-By: ambari' -X GET "http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster?fields=hosts/Hosts/host_name,hosts/Hosts/host_state" | grep -B1 host_state
. OR # curl -u admin:admin -H 'X-Requested-By: ambari' -X GET "http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster?fields=hosts/Hosts/host_name,hosts/Hosts/host_state" | grep -B1 HEARTBEAT_LOST
OUTPUT
-------
"host_name" : "hdfcluster4.example.com",
"host_state" : "HEARTBEAT_LOST" . For healthy nodes we can grep like: # curl -u admin:admin -H 'X-Requested-By: ambari' -X GET "http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster?fields=hosts/Hosts/host_name,hosts/Hosts/host_state" | grep -B1 HEALTHY
OUTPUT
-------
"host_name" : "hdfcluster1.example.com",
"host_state" : "HEALTHY"
--
"host_name" : "hdfcluster2.example.com",
"host_state" : "HEALTHY"
--
"host_name" : "hdfcluster3.example.com",
"host_state" : "HEALTHY"
.
... View more
03-20-2018
06:22 AM
@Michael Bronson From Ambari side currently we only have features to remove the OLD stacks, as mentioned in the following JIRA and HCC thread: https://issues.apache.org/jira/browse/AMBARI-18435 https://community.hortonworks.com/questions/21876/how-to-remove-an-old-hdp-version.html . But if you want to remove the *all new rpm's* then ambari does not provide that option. You will have to rely on the yum command itself and try something like: Please be careful with the following command before running the below one. I am assuming you have the new HDP RPMs version as "2.6.4.0-91" then you might want to try something like following ( -y option at the end of below command will make it non interactive mode) # yum remove "*2.6.4.0-91*"
... View more
03-19-2018
11:05 PM
@Michael Bronson I will suggest to do a "Stop All" and "Start All" for all services from ambari UI and then try again We must see some errors/warning in ambari server log or in agent logs ... to understand why The false Warnings are being shown in the UI. Or may be the DB inconsistency would have caused it.
... View more
03-19-2018
10:18 PM
@Ajay Jayswal If you find the above answer helped in finding and fixing the improper Hostname/resolution issue then please makr this thread as Answered by clicking on the "Accept" button. That way this troubleshooting step will be useful for other HCC users as well.
... View more
03-19-2018
12:19 PM
@Harish123 Reddy Please share the "/var/log/ambari-server/ambari-server.log" and "ambari-server.out" file. It must provide us information like some Errors which is causing ambari server failure. Also please make sure that the Ambari DB is up and running.
... View more
03-19-2018
08:25 AM
1 Kudo
@Michael Bronson I see 4 messages in your Initial Issue description. Message-1). Verify Cluster Components Exist In Target Repository This kind of message can appear while starting upgrades if we have installed some custom services to our cluster which are not part of the HDP version that we are going to install. For example if you have some third party services installed in your cluster which are not coming from HDP repo then you will have to remove them before you begin the HDP upgrade. Message-2). All service components must be installed This messages indicates that you might have some services installed to your cluster which migth have some components in "INSTALL_FAILED" state. # curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster/host_components?HostRoles/state=INSTALL_FAILED If you find any component in install failed state then please install them properly before starting the upgrade. In some cases it might happen if the clients components might not be installed on few cluster hosts. So please check if you have CLIENT components installed properly on your cluster nodes. If not then use the following API aapproach to install the CLIENTs to your cluster nodes. (or install them using Ambari UI) https://community.hortonworks.com/content/supportkb/150098/how-to-install-hadoop-clients-on-all-the-hosts-in.html Message-3). No Service can be in maintenance mode. You can not start HDP upgrade if any of your service is in Maintenance mode so please run the following API call before upgrading HDp to findout if there are any Services in Maintenance Mode or not? Also similar approach you will need to use to check that all Host Components are also not in Maintenance Mode . # curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster/services?ServiceInfo/maintenance_state=ON Message-4). All Services must be started. This message indicates that we can not start HDP component upgrades before all the components are already in running state. So we need to make sure that all the components / services are in Started stated. Also please make sure that we must run all the service checks successfully before we begin the HDP component upgrade to verify that all the components are in healthy state..
... View more
03-17-2018
10:14 PM
@Ajay Jayswal Please check your "ambari-metrics-monitor.out" file to see if you notice any such following message whcih indicates that the Ambari Metrics Monitor process on that node (niode2) has some issues connecting to the AMS collector? [WARNING] emitter.py:146 - Error sending metrics to server. [Errno 111] Connection refuse
.
.
[WARNING] emitter.py:120 - Metric collector host xxxxx.yyyy.com was blacklisted. . Also please check if the metrics monitor on that host is pointing to the correct Hostname of the AMS collector? Also do a telnet or (netcat) to see if node2 is able to connect to AMS collector Hostname & Port or not? # grep 'metrics_servers' /etc/ambari-metrics-monitor/conf/metric_monitor.ini
metrics_servers = amb25102.example.com
# grep 'port' /etc/ambari-metrics-monitor/conf/metric_monitor.ini
port = 6188
# nc -v amb25102.example.com:6188 .
... View more
03-17-2018
10:06 PM
@Ajay Jayswal monitor might be running but is it communicating well with AMS collector or not? Please share the log "/var/log/ambari-metrics-monitor/ambari-metrics-monitor.out" can you please try this: (basically rebuild psutils) # cd /usr/lib/python2.6/site-packages/resource_monitoring/
# python psutil/build.py The from amabri UI restart the AMS monitor process on that node2
... View more