Got it

The ZooKeeper client is AuthFailed

Created: Mar 20, 2020 05:59:43Latest reply: Mar 20, 2020 06:04:19 555 1 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello all,

In clusters security mode, when the HiveServer service is normal and SQL is executed by using the JDBC interface to connect to HiveServer, "The ZooKeeper client is AuthFailed" is reported.


14/05/19 10:52:00 WARN utils.HAClientUtilDummyWatcher: The ZooKeeper client is AuthFailed 

 14/05/19 10:52:00 INFO utils.HiveHAClientUtil: Exception thrown while reading data from znode.The possible reason may be connectionless. This is recoverable. Retrying..  

 14/05/19 10:52:16 WARN utils.HAClientUtilDummyWatcher: The ZooKeeper client is AuthFailed  

 14/05/19 10:52:32 WARN utils.HAClientUtilDummyWatcher: The ZooKeeper client is AuthFailed  

 14/05/19 10:52:32 ERROR st.BasicTestCase: Exception: Could not establish connection to active hiveserver  

 java.sql.SQLException: Could not establish connection to active hiveserver


Thanks for help.


Featured Answers
little_fish
Admin Created Mar 20, 2020 06:04:19

Dear Phany,

Here is the solution for AuthFailed.

  1. Ensure that the user can properly access the user.keytab file in related paths on the client node.

  2. Ensure that the user's user.principal that is used corresponds to the specified keytab file.

    Run the klist -kt keytabpath/user.keytab command to check it.

  3. If the cluster switches the domain name, the principal field used in the URL must be a new domain name.

    For example, the default value is hive/hadoop.hadoop.com@HADOOP.COM. If the cluster has switched the domain name, the field must be changed accordingly. For example, if the domain name is abc.com, it is hive/hadoop.abc.com@ABC.COM.

  4. Ensure that authentication is normal and HiveServer can be connected.

    Run the following commands on the client:

    source $client_home/bigdata_env

    kinit username

    Run the beeline command on the client to ensure normal running.

    Thanks.


View more
  • x
  • convention:

All Answers

Dear Phany,

Here is the solution for AuthFailed.

  1. Ensure that the user can properly access the user.keytab file in related paths on the client node.

  2. Ensure that the user's user.principal that is used corresponds to the specified keytab file.

    Run the klist -kt keytabpath/user.keytab command to check it.

  3. If the cluster switches the domain name, the principal field used in the URL must be a new domain name.

    For example, the default value is hive/hadoop.hadoop.com@HADOOP.COM. If the cluster has switched the domain name, the field must be changed accordingly. For example, if the domain name is abc.com, it is hive/hadoop.abc.com@ABC.COM.

  4. Ensure that authentication is normal and HiveServer can be connected.

    Run the following commands on the client:

    source $client_home/bigdata_env

    kinit username

    Run the beeline command on the client to ensure normal running.

    Thanks.


View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.