Support Questions
Find answers, ask questions, and share your expertise

In Ambari All the services are running but for clients its saying 0 client installed

I have done HDP Rolling Upgrade. The services are all running fine. However, all the clients which are there they are in red(triangle state) , even when I refresh the configs the operation successfully completes but the client does not start. Do you know what could be the potential root cause or what needs to be done.

8 REPLIES 8

Super Mentor

@sanjeevan mahajan

It will require further investigation to know why did it happen after the upgrade. But i guess that the Ambari Database might not be having the correct entry for the clients. May be looking at the ambari-server.log and ambari-agent logs from those hosts can help.

So you might want to run the following Ambari API commands to see if it fixes your issue, By moving the sate of thse clients to "INSTALLED"

Example:

# curl -u admin:admin -H "X-Requested-By:ambari" -i -X PUT -d '{"RequestInfo":{"context":"Install Client"},"Body":{"HostRoles":{"state":"STARTED"}}}' http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<CLUSTER_HOST1>/host_components/YARN_... 

# curl -u admin:admin -H "X-Requested-By:ambari" -i -X PUT -d '{"RequestInfo":{"context":"Install Client"},"Body":{"HostRoles":{"state":"INSTALLED"}}}' http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<CLUSTER_HOST1>/host_components/ZOOKE...

# curl -u admin:admin -H "X-Requested-By:ambari" -i -X PUT -d '{"RequestInfo":{"context":"Install Client"},"Body":{"HostRoles":{"state":"STARTED"}}}' http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<CLUSTER_HOST1>/host_components/HDFS_... 

# curl -u admin:admin -H "X-Requested-By:ambari" -i -X PUT -d '{"RequestInfo":{"context":"Install Client"},"Body":{"HostRoles":{"state":"STARTED"}}}' http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<CLUSTER_HOST1>/host_components/HBASE... 


# curl -u admin:admin -H "X-Requested-By:ambari" -i -X PUT -d '{"RequestInfo":{"context":"Install Client"},"Body":{"HostRoles":{"state":"STARTED"}}}' http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<CLUSTER_HOST1>/host_components/HIVE_... 

.

You will need to change the AMBARI_HOST, CLUSTER_NAME and the hosts' FQDN in which the respective clients should be installed: "CLUSTER_HOST1" (example: erie1.example.com/erie2.example.com ....)

.

Also please check the output of the following SQL query on Ambari DB to verify that the clients are not in INIT state.

SELECT * FROM hostcomponentdesiredstate WHERE component_name LIKE '%CLIENT';

Like:

14037-installed-and-started-clients.png

.

@JaySenSharma : Actually if I run yum list sqoop command. It does not show me the package in the version which I have installed.

yum list sqoop

Loaded plugins: changelog, downloadonly, kabi Loading support for Red Hat kernel ABI Available Packages sqoop.noarch 1.4.6.2.5.3.0-37.el6 HDP-2.4.3.0

HDP-2.4.3.0 is the older version, I have upgraded it to a new version of HDP 2.4.3.X.X which is a patched version

Super Mentor

@sanjeevan mahajan

Which version you were expecting to be displayed in the output "yum list sqoop" ?

Also can you please share the output of the following command so that we can see if any of the package/component is not upgraded properly.

# hdp-select
# rpm -qa | grep sqoop

.

Also do you see any such service information in the DB? It should show the version information as well.

SELECT * FROM hostcomponentstate where service_name = 'SQOOP';

.

I was expecting 2.4.3.13-1 .

The output is below :

hdp-select

accumulo-client - None accumulo-gc - None accumulo-master - None accumulo-monitor - None accumulo-tablet - None accumulo-tracer - None atlas-server - 2.4.3.13-1 falcon-client - 2.4.3.13-1 falcon-server - 2.4.3.13-1 flume-server - None hadoop-client - 2.4.3.13-1 hadoop-hdfs-datanode - 2.4.3.13-1 hadoop-hdfs-journalnode - 2.4.3.13-1 hadoop-hdfs-namenode - 2.4.3.13-1 hadoop-hdfs-nfs3 - 2.4.3.13-1 hadoop-hdfs-portmap - 2.4.3.13-1 hadoop-hdfs-secondarynamenode - 2.4.3.13-1 hadoop-httpfs - 2.4.3.13-1 hadoop-mapreduce-historyserver - 2.4.3.13-1 hadoop-yarn-nodemanager - 2.4.3.13-1 hadoop-yarn-resourcemanager - 2.4.3.13-1 hadoop-yarn-timelineserver - 2.4.3.13-1 hbase-client - 2.4.3.13-1 hbase-master - 2.4.3.13-1 hbase-regionserver - 2.4.3.13-1 hive-metastore - 2.4.3.13-1 hive-server2 - 2.4.3.13-1 hive-webhcat - 2.4.3.13-1 kafka-broker - None knox-server - 2.4.3.13-1 livy-server - None mahout-client - None oozie-client - 2.4.3.13-1 oozie-server - 2.4.3.13-1 phoenix-client - 2.4.3.13-1 phoenix-server - 2.4.3.13-1 ranger-admin - 2.4.3.13-1 ranger-kms - 2.4.3.13-1 ranger-usersync - 2.4.3.13-1 slider-client - 2.4.3.13-1 spark-client - 2.4.3.13-1 spark-historyserver - 2.4.3.13-1 spark-thriftserver - 2.4.3.13-1 sqoop-client - 2.4.3.13-1 sqoop-server - 2.4.3.13-1 storm-client - 2.4.3.13-1 storm-nimbus - 2.4.3.13-1 storm-slider-client - 2.4.3.13-1 storm-supervisor - 2.4.3.13-1 zeppelin-server - None zookeeper-client - 2.4.3.13-1 zookeeper-server - 2.4.3.13-1

rpm -qa | grep sqoop sqoop_2_4_2_0_258-1.4.6.2.4.2.0-258.el6.noarch sqoop_2_4_3_13_1-1.4.6.2.4.3.13-1.el6.noarch sqoop_2_4_3_0_227-metastore-1.4.6.2.4.3.0-227.el6.noarch sqoop_2_2_4_10_1-1.4.5.2.2.4.10-1.el6.noarch sqoop_2_2_4_10_1-metastore-1.4.5.2.2.4.10-1.el6.noarch sqoop_2_4_3_13_1-metastore-1.4.6.2.4.3.13-1.el6.noarch sqoop_2_4_2_0_258-metastore-1.4.6.2.4.2.0-258.el6.noarch sqoop_2_4_3_0_227-1.4.6.2.4.3.0-227.el6.noarch

Super Mentor

@sanjeevan mahajan

HDP Upgrade does not uninstall old packages from the host machine, but only installs newer versions so you should see old and the current version both.

The "hdp-select" command output shows that your current sqoop version is following (which is upgraded one):

sqoop-client - 2.4.3.13-1 
sqoop-server - 2.4.3.13-1

Howver you can find the current verison of sqoop that is actually being used using the following command

# sqoop version

.

There is a feature request raised for the same : https://issues.apache.org/jira/browse/AMBARI-18435

- With this feature in Ambari 2.5 you should be able to remove the older HDP packages installed on the host. For more information on this please refer to: https://community.hortonworks.com/questions/21876/how-to-remove-an-old-hdp-version.html

.

@Jay SenSharma Yes it is pointing to the correct version 2.4.3.13-1. Nothing is there in Ambari logs as well

@Jay SenSharma Yes it is pointing to the correct version 2.4.3.13-1. Nothing is there in Ambari logs as well

Super Mentor

@sanjeevan mahajan

As long as you see that the "hdp-select" output is showing the correct desired version for the installed packages on all hosts nothing to worry about (in terms of version conflict)

Further verification can be done by running the version command on individual binaries like:

# sqoop version | grep Sqoop
Sqoop 1.4.6.2.5.3.0-37

# hdfs version | grep Hadoop
Hadoop 2.7.3.2.5.3.0-37

.

You can also check that the sqoop conf directory is pointing to the "current" which is symlink to the current verison like

# ls -lan /etc/sqoop/conf
lrwxrwxrwx. 1 0 0 34 Feb 13 14:29 /etc/sqoop/conf -> /usr/hdp/current/sqoop-client/conf

.

# ls -lan /usr/hdp/current | grep sqoop
lrwxrwxrwx. 1 0 0  25 Mar 25 12:30 sqoop-client -> /usr/hdp/2.4.3.13-1/sqoop
lrwxrwxrwx. 1 0 0  25 Mar 25 12:30 sqoop-server -> /usr/hdp/2.4.3.13-1/sqoop

.

# ls -lan /usr/hdp
total 24
drwxr-xr-x.  6 0 0 4096 Jan 25 07:03 .
drwxr-xr-x. 15 0 0 4096 Aug 18  2016 ..
drwxr-xr-x. 32 0 0 4096 Oct 27 09:17 2.4.3.13-1
drwxr-xr-x. 45 0 0 4096 Feb 13 13:05 2.4.2.0-258
drwxr-xr-x.  2 0 0 4096 Mar 25 12:30 current

.

Still if you find any issue then you can always "uninstall and install" the clients from ambari UI. As these are simple client binaries so it should not have any negative impact to your cluster.