It is quite common from lots of Hadoop clusters that after enabling Load Balancer for certain services that have Kerberos already, the connection to those services via Load Balancer will fail. However, the direct connection to them will always successful. The typical errors returned looks like below: In case of …
I have seen lots of users complain about seeing lots of “No data or no sasl data in the stream” errors in the HiveServer2 server log, yet they have not noticed any performance impact nor query failure for Hive. So I think it would be good to write a blog …
Currently Cloudera Manager does not support setting up multiple KDCs for the krb5.conf file natively, this article explains the workarounds we can have using the existing feature provided by Cloudera Manager. This article also assumes that you have krb5.conf file managed by Cloudera Manager. If you are using Cloudera Manager …
When generating credentials through Cloudera Manager, sometimes Cloudera Manager will return you the following error: If you see the similar error and you know that you have AD enabled for your cluster, then you have landed on the right place. This is likely caused by a bug in Cloudera Manager …
The following is the scenario of the cross domain problem with Kerberized cluster: 1. Cluster is within realm “DEV.EXAMPLE.COM” 2. Client is outside cluster with realm “EXAMPLE.COM” 3. Connect to Impala from client machine works 4. Connect to HS2 from client machine does not work and get the following error: …
My new Snowflake Blog is now live. I will not be updating this blog anymore but will continue with new contents in the Snowflake world!