Hi @ThomasCloudeara ,  First, the JDBC driver v2.6.4 is very old. Kindly use the latest one, download it from our website: https://www.cloudera.com/downloads/connectors/impala/jdbc/ Preferably use the "JDBC4.2" specification driver, with that use "com.cloudera.impala.jdbc.Driver" instead. Second, please follow the guide https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-30/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf and verify the JDBC connection string: - if the LDAP authentication is really enabled (AuthMech=3 tells that) or if you have Kerberos authentication only in your cluster (which needs AuthMech=1) - if LDAP auth is really enabled, can you connect to Impala with impala-shell with the same username/password pair?    Thanks  Miklos ... View more

Hi @StuartM , I know it's not a direct answer, but this requirement sounds more like a good call for Kafka - which inherently supports the idea of "consumer offsets". ... View more

These are pretty long GC pauses, I assume they are from the HMS logs. With long GC pauses of course every operation will suffer and will be slow, eventually the SMON's request will time out . Kindly review the HMS heap size and consider to increase it until you get a stable performance (without such GC pauses). ... View more

Hi @hanumanth , I assume this is a CDH 6 cluster. Do you have Sentry enabled as well? Is this always happening, or just at some times? Have you tested in beeline how long does it take to drop an example database? Does it also fail with a timeout? I guess it is taking more than 60 seconds (that's the service monitor's default timeout), and since the default timeout for HS2 to HMS is 5 minutes it actually succeeds. Thanks, Miklos   ... View more