If the query didn't fail immediately after the error "[Cloudera][ODBC] (11180) SQLGetInfo property not found", we can ignore this error message. Or you can try UseNativeQuery option to avoid this kind of messages. From the point of my view,  "Invalid query handle" was most likely the cause. If I were you, I would check if the query or session timed out or cancelled. If there is a load balancer, I'd also check if the LB sent the request to a wrong impala daemon by chance. ... View more

You mentioned that you could connect to Impala without user and password. I suppose you didn't change the authentication mechanism but only enabled SSL for Impala service. Then what you need to do is to add SSL, SSLKeyStore and SSLKeyStorePwd into your JDBC connection string:   jdbc:impala://Impala_Daemon_Host:21050/default;SSL=1;SSLKeyStore=<keystore.jks>;SSLKeyStorePwd=<keystore_pwd>   You don't need UID and PWD unless you have to set AuthMech to 3 which is usually required when Impala uses LDAP authentication.  ... View more

Hi Amn,   The message was "1 errors(s) seen monitoring completed queries". It was reported by CM agent. You should be able to find error messages in detail from cloudera-scm-agent.log*.  The ShortCircuitCache message was from HDFS API. You can ignore it as it's a warning message.  HDFS API should retry and bypass ShortCircuitCache if ShortCircuitCache fails.   Regards, Robbie ... View more

Hi Amn,   Your issue is different from which is addressed in the KB article. CM agent collects archived query profiles from Impala Daemon and saves to CM database periodically. According to your logs, the file /var/log/impalad/profiles/impala_profile_log_1.1-1574308887326 was gone when CM agent tried to open it: [21/Nov/2019 17:39:58 +0000] 5415 Monitor-HostMonitor throttling_logger ERROR (2 skipped) Failed to collect NTP metrics Traceback (most recent call last): File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.16.2-py2.7.egg/cmf/monitor/host/ntp_monitor.py", line 48, in collect self.collect_ntpd() ... File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/ClusterStatsLogStreaming-UNKNOWN-py2.7.egg/clusterstats/log/streaming/file.py", line 41, in open_log_file handle = open(self.__path) IOError: [Errno 2] No such file or directory: '/var/log/impalad/profiles/impala_profile_log_1.1-1574308887326'  I suggest you investigate why the file was gone. How often do you see this kind of error? ... View more

If you have a support contract with Cloudera, you can contact us via details at the following link under ‘How can I contact support?’ and we will be happy to assist: https://my.cloudera.com/faq.html#support If you do not yet have a support contract with Cloudera, you would need to first speak with a sales representative in order to contract with support via the following link: https://www.cloudera.com/contact-sales.html ... View more

Usually, I would inspect the profiles of failed queries to get rough ideas, then determine which logs I should check next. If you have a contract with Cloudera, it's worth to file a ticket. Cloudera Support will help you troubleshoot step by step. ... View more

Several reasons can cause this error.  Check your ODBC settings and application/ODBC driver versions. For example, if one side is keberized/SSL enabled but another side isn't, or a 32bit application runs against 64bit ODBC driver, you can see this kind of error. If all look good, you need to check Impala ODBC Driver logs to find more details. ... View more