Member since
09-22-2015
7
Posts
1
Kudos Received
0
Solutions
07-04-2024
10:04 PM
1 Kudo
Found another Cloudera KB, where it says: To resolve this issue we have to set this property hadoop.security.authorization to false under hive safety valve as this will be used only by Hive without impacting the storage, since it cannot be set to false at storage layer as it is needed for storage. STEPS TO SET THE PROPERTY: CM < Hive on tez < Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml Name: hadoop.security.authorization Value: false
... View more
05-11-2020
08:52 PM
Hi Team, We are also facing similar issues. Traceback (most recent call last): File "/opt/cloudera/cm-agent/lib/python2.6/site-packages/cmf/agent.py", line 1525, in handle_heartbeat_response self._handle_heartbeat_response(response) File "/opt/cloudera/cm-agent/lib/python2.6/site-packages/cmf/agent.py", line 1658, in _handle_heartbeat_response self._update_parcel_activation_state(response) File "/opt/cloudera/cm-agent/lib/python2.6/site-packages/cmf/agent.py", line 1569, in _update_parcel_activation_state manage_old_parcels = old_response.get("create_parcel_symlinks") AttributeError: 'NoneType' object has no attribute 'get' Tried to hard restart the agent, but no luck. Could anyone help?
... View more
01-12-2020
12:02 PM
Hi All, Was there any solution for the above issue. I am facing similar problem. I have made changes in livy to disbale connecting to hive (enableHiveSupport() to false), however, when I trying to submit via pyspark, it connecting to hive and failing with Kerberos error. Tried to execute the same using spark and works as expected. Any thoughts? Thanks Vijith Vijayan
... View more
08-22-2018
10:57 PM
Thank you @bgooley. Will be able to clarify the below query? When comparing to other host (like below). Does that mean it try to connect with UDP first and then switched to TCP? >>> KrbKdcReq send: kdc=****** UDP:88, timeout=3000, number of retries =3, #bytes=2247 >>> KDCCommunication: kdc=****** UDP:88, timeout=3000,Attempt =1, #bytes=2247 >>> KrbKdcReq send: #bytes read=104 >>> KrbKdcReq send: kdc=****** TCP:88, timeout=3000, number of retries =3, #bytes=2247 >>> KDCCommunication: kdc=****** TCP:88, timeout=3000,Attempt =1, #bytes=2247 >>>DEBUG: TCPClient reading 2722 bytes >>> KrbKdcReq send: #bytes read=2722 If so, what could be the reason the affected host is not switching in similar manner. If that is with firewall, then how is it working when we add paramater udp_preference_limit to connect with TCP? Thanks you Vijith
... View more
08-21-2018
04:52 PM
I was using a custom krb5.conf and it didn't work. Next I tried to change /etc/krb5.conf and then worked. Just wondering why it is not possible with UDP?
... View more
08-20-2018
11:39 PM
Hi, We are facing similar issue. Not able execute any hadoop commands from the node and services like Datanode, Node manager are not starting on the node. Please find the log below when I executed the command HADOOP_ROOT_LOGGER=TRACE,console HADOOP_JAAS_DEBUG=true HADOOP_OPTS="-Dsun.security.krb5.debug=true" hdfs dfs -ls / Affected node - Seems kdc is connecting using UDP and not TCP >>> Credentials acquireServiceCreds: same realm default etypes for default_tgs_enctypes: 23 1 3. >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType >>> EType: sun.security.krb5.internal.crypto.ArcFourHmacEType >>> KdcAccessibility: reset >>> KrbKdcReq send: kdc=***** UDP:88, timeout=3000, number of retries =3, #bytes=2247 >>> KDCCommunication: kdc=****** UDP:88, timeout=3000,Attempt =1, #bytes=2247 SocketTimeOutException with attempt: 1 >>> KDCCommunication: kdc=****** UDP:88, timeout=3000,Attempt =2, #bytes=2247 SocketTimeOutException with attempt: 2 >>> KDCCommunication: kdc=****** UDP:88, timeout=3000,Attempt =3, #bytes=2247 SocketTimeOutException with attempt: 3 >>> KrbKdcReq send: error trying ******:88 java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive0(Native Method) at java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:145) Another node from the same rack which is working fine >>> Credentials acquireServiceCreds: same realm default etypes for default_tgs_enctypes: 23 1 3. >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType >>> EType: sun.security.krb5.internal.crypto.ArcFourHmacEType >>> KdcAccessibility: reset >>> KrbKdcReq send: kdc=****** UDP:88, timeout=3000, number of retries =3, #bytes=2247 >>> KDCCommunication: kdc=****** UDP:88, timeout=3000,Attempt =1, #bytes=2247 >>> KrbKdcReq send: #bytes read=104 >>> KrbKdcReq send: kdc=****** TCP:88, timeout=3000, number of retries =3, #bytes=2247 >>> KDCCommunication: kdc=****** TCP:88, timeout=3000,Attempt =1, #bytes=2247 >>>DEBUG: TCPClient reading 2722 bytes >>> KrbKdcReq send: #bytes read=2722 >>> KdcAccessibility: remove ****** :88 >>> EType: sun.security.krb5.internal.crypto.ArcFourHmacEType >>> KrbApReq: APOptions are 00100000 00000000 00000000 00000000 >>> EType: sun.security.krb5.internal.crypto.ArcFourHmacEType Krb5Context setting mySeqNumber to: 83326031 Created InitSecContextToken: We then tried to force krb to use tcp by below method. Added below parameter to krb5.conf but didn't help udp_preference_limit =1 Thanks Vijith Vijayan
... View more