https://community.cloudera.com/t5/Support-Questions/Beeline-uses-incorrect-kerberos-principal-for-zookeeper/m-p/326212#M229820 <P>I tried adding the parameter like this:</P><P>```</P><P>/opt/hadoop/hive/bin/hive --config /etc/hive/conf.s2 --service beeline -u "jdbc:hive2://master-01.com:2181,master-02.com:2181,master-03.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;principal=zookeeper-mycluster/_HOST@REALM.COM;sslTrustStore=/etc/ssl/certs/truststore.jks;trustStorePassword=****"</P><P>```</P><P>...and the default zookeeper principal name is unchanged (verified in the krb5kdc.log file on the KDC:</P><P>&nbsp;</P><P>```</P><P>Oct 04 09:15:00 master-01.com krb5kdc[6869](info): TGS_REQ (4 etypes {18 17 16 23}) 192.168.32.15: LOOKING_UP_SERVER: authtime 0, hive-mycluster/master-03.com@REALM.COM for zookeeper/master-02.com@REALM.COM, Server not found in Kerberos database</P><P>```</P> Mon, 04 Oct 2021 09:21:25 GMT alxKd 2021-10-04T09:21:25Z