Member since
03-06-2020
398
Posts
54
Kudos Received
35
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
152 | 11-21-2024 10:12 PM | |
1004 | 07-23-2024 10:52 PM | |
1144 | 05-16-2024 12:27 AM | |
3251 | 05-01-2024 04:50 AM | |
1417 | 03-19-2024 09:23 AM |
08-30-2023
06:03 AM
Hi, The error message you provided, "Server not found in Kerberos database (7) - LOOKING_UP_SERVER," is indicating an issue with the Kerberos authentication process. This error usually occurs when the Kerberos client is unable to find the server's principal in the Kerberos database. Below is the article to troubleshoot kerberos related issues: https://community.cloudera.com/t5/Customer/Troubleshooting-Kerberos-Related-Issues-Common-Errors-and/ta-p/76192 > Please check if Ensure that DNS is correctly configured for both the client and the server. The client should be able to resolve the hostname of the server to the correct IP address. > Make sure the clocks of the client, server, and KDC are synchronized. Time differences beyond the tolerance set in Kerberos configuration can cause authentication failures. > Ensure that the Key Distribution Center (KDC) is reachable and operational. > Verify that the krb5.conf file on the client machine is correctly configured with the appropriate realms, KDCs, and other Kerberos settings. Regards, Chethan YM
... View more
08-30-2023
05:51 AM
Hello, May i know what is the exact issue? Can you attach the error stack trace OR screenshots? If the connection itself is failing then we do not get the query id. If the connection is succeeded and query is failing then we can see the query profile in the CM -> Impala -> queries section. OR atleast we can see the query id in the impala coordinator logs. Regards, Chethan YM
... View more
08-29-2023
08:51 AM
Hi @hebamahmoud You mean even after configuring the KUDU-HMS integration you are still facing the same issue/error? Can you confirm? Have you followed the given workaround on all HMS servers? https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/runtime-release-notes/topics/rt-pvc-known-issues-kudu.html If that does not work can you try below and check? CM > kudu > configuration> kudu service Advanced Configuration Snippet (Safety Valve) ==> --trusted_user_acl=impala,hive and restart the kudu services, Regards, Chethan YM
... View more
07-21-2023
01:02 AM
Hi, I do not think we have such option to create a view along with query option, you can follow any one of below: > Set the query option at session level before running the query. > Add this query option globally in impala configurations -> "default_query_options" section. > Add it in impala admission control pool for a specific pool where this query runs, edit the pool and add the property into "Default query options" section. Regards, Chethan YM
... View more
07-19-2023
03:13 AM
Hi , I think you need to check with Power BI team whether setting parameters at session level is supported or not. It's an issue/limitation at client side.
... View more
05-31-2023
05:58 AM
Hi, -> Have you tried restarting namenodes after adding the group name? -> The property name is "Superuser Group" , the "vega" is username or group name? If it is user name make sure there is "vega" group as well where "vega" user is part of and give a try again. Regards, Chethan YM
... View more
05-29-2023
05:37 AM
Hi, I did not get the recommended size of kudu table, But there is a limitation like what is amount of data per tablet, how many tablets per table etc.. Please refer the below documentation: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/kudu_limitations.html#scaling_limits Regards, Chethan YM
... View more
05-19-2023
02:21 AM
Yes, User group mapping should be across the cluster nodes not only on name-node.
... View more
05-18-2023
02:05 AM
Hi, Use the below commands and see if you find any difference. CREATE ROLE [role_name]; GRANT <PRIVILEGE> ON <OBJECT> <object_name> TO ROLE <roleName> GRANT ROLE <role_name> TO GROUP <groupName>; Examples: create role testing; grant all on database <db-name> to role testing; grant role testing to group <group-name>; In this case the user should be part of this particular group on all the cluster nodes - user group mapping at OS level is required. You can check the groups of a user using "id <user-name>". Regards, Chethan YM
... View more
05-03-2023
03:33 AM
Hi, Is Impala session hang means not able to run any queries? Is this issue observed via hue or impala-shell? repro the issue via impala-shell and check the coordinator logs to get any suspected error messages. At the time of issue check the cluster load how may queries running concurrently, Issue may arise if any expensive/complex operations are running. Do not frequently run "invalidate metadata" query in the cluster it is one of the expensive operations and it pressurises the catalog service. Regards, Chethan YM
... View more