@kotesh banoth Can you try without SASL, or somehow it need to be imported in your python. Pleas try this with NOSASL to see what you get next: (or verify if the "cyrus-sasl-devel" is installed properly) conn = hive.connect(host='172.16.0.XXX', port=10000, username='kotesh', auth='NOSASL') . It will need to following config on your hive side. <property> <name>hive.server2.authentication</name> <value>NOSASL</value> </property> . ... View more

@kotesh banoth Good to see that this time you are not getting the "Import Error: libsasl.2.so.2" The current error seems to be related to connectivity: thrift.transport.TTransport.TTransportException: Could not connect to any of [('172.16.0.125', 10000)] . So there can be two reasons , Either you do not have a valid Kerberos Ticket Or you do not have the connectivity from your host to 172.16.0.125 on port 10000 So please check the following: 1. Check if you can access the 172.16.0.125 on port 10000, From the host where you are running the python code. # nc -v 172.16.0.125 10000 OR # telnet 172.16.0.125 10000 2. Please check that before running the python code , you have a valid kerberos ticket, Because in your code we see that you are using kerberos. So using the following command please check if you have a valid ticket or not? # klist . 3. Also please check your code to find out if you are using correct IP Address or not? Because in your original post we see a different Address was used instead of 172.16.0.125 conn = hive.Connection(host="192.168.1.100", port=10000, auth="KERBEROS", database="bmdatalake", kerberos_service_name= "hive") . ... View more

@uri ben-ari If the button is still disabled to change the NodeManger Heap then please make sure that you have logged in with correct user who has access to change to configuration . (not as Read Only User). Please see : https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.1.0/bk_ambari-administration/content/cluster_roles.html ... View more

@kotesh banoth In your case the version it is expecting as "libsasl.2.so.2" so please check if you can reinstall that package: Reference: https://github.com/cloudera/python-sasl/issues/9 Not sure if the following will work at your end or not but worth trying: sudo yum install cyrus-sasl-devel OR sudo pip install sasl . ... View more

@kotesh banoth Do you have the library ? # ls -l /usr/lib64 | grep libsasl lrwxrwxrwx. 1 root root 17 Dec 1 2014 libsasl2.so.3 -> libsasl2.so.3.0.0 -rwxr-xr-x. 1 root root 121296 Jun 10 2014 libsasl2.so.3.0.0 . ... View more

@Shrikant BM 1. What is the Size of your Cluster? If the cluster size is large then sometimes we need to tune the "agent.threadpool.size.max" agent.threadpool.size.max" : property sets max number of threads used to process heartbeats from ambari agents. The default value for this property is "25". This basically indicates the size of the Jetty connection pool used for handling incoming Ambari Agent requests. # grep 'agent.threadpool.size.max' /etc/ambari-server/conf/ambari.properties 50 . For more detail on this please refer to: https://community.hortonworks.com/articles/131670/ambari-server-performance-tuning-troubleshooting-c.html . 2. If the heartbeat be coming back shortly (in few seconds) then another approach will be to increase the "Ambari Agent Heartbeat" interval from 2 minutes to bit more. Ambari UI --> Alerts --> Search for "Ambari Agent Heartbeat" . 3. Please share the ambari-server.log and ambari-agent logs of the same time stamp when you notice the heartbeat lost ... so that we can review for any strange behaviour. . 4. If the heartbeat lost is happening on a specific duration (time pattern) then we should check if any heavy load job is running on the agent host that might be causing the Agent to not send the heartbeat for few seconds. . ... View more