Member since
02-28-2022
166
Posts
14
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
367 | 07-07-2025 06:35 AM | |
377 | 06-17-2025 09:42 AM | |
1509 | 04-02-2025 07:43 AM | |
601 | 10-18-2024 12:29 PM | |
10258 | 09-05-2024 09:06 AM |
09-05-2025
11:04 AM
hi @Bhar , check if this post helps you: https://community.cloudera.com/t5/Support-Questions/how-to-install-python-libs-in-the-python-engine-of-the-quot/td-p/391589
... View more
09-04-2025
05:27 AM
hi @huimin, perfect! if you could describe the solution you implemented, it will help others who encounter the same issue. hugs.
... View more
08-08-2025
10:21 AM
Hive logging is configured on /etc/hive/conf/hive-log4j2.properties. Look for these: property.hive.log.dir property.hive.log.file That is the log location you are looking for Thanks, -JMP
... View more
07-31-2025
10:57 AM
The "Clock skew too great" error in your release (which is out of maintenance due to its age) usually happens when the daemon is overloaded and KRPC is *not* enabled (--use_krpc=false in the Impala safety valve). That is likely why you see those errors. Although - certain overload conditions trigger unusual errors regardless. That is likely why you get the rejection on any client. You can try several things: a. make sure "--use_krpc=false" is not in the current Impala configs b. adjust the workload c. if you get the error with near zero load *after the coordinator restart* that definitely points at a network issue as I have alluded to before d. make sure the coordinator host's kernel settings are adequate: kernel.pid_max = 1048480 vm.max_map_count = 1048480 kernel.pid_max = 2000000 vm.max_map_count = 8000000
... View more
07-30-2025
09:33 PM
Yes, @Malrashed, that should help as well. Mainly we are bypassing the warning by increasing the threshold
... View more
07-28-2025
01:09 PM
hi @RamaClouder, current scenario: You're running CDP in the cloud, using the CDP Public Cloud, right? if so, you have technical support included with your license. For more accurate and responsive support, we recommend opening a case in the "My Cloudera" portal as S1, and support will assist you as soon as possible. if not, please return with the stderr and stdout logs for more details. tip: Check permission settings in IAM, broker, etc.
... View more
07-14-2025
09:44 PM
@vineetchaure, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.
... View more
07-04-2025
11:19 AM
@Jackallboy Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. If you are still experiencing the issue, can you provide the information requested? Thanks.
... View more
07-02-2025
01:34 PM
hi @rizalt , from your report, you probably have snapshots enabled for this directory, so any delete in this directory will not be 100% effective unless the snapshot is also deleted. deleting the snapshot will make it impossible to recover data if necessary. so, on the namenode webui page, in the "snapshot" tab, check your snapshots.
... View more
07-02-2025
01:24 PM
hi @Rajat_jangra in CDH you will have to filter the Hive and Impala logs to know when the tables were accessed. i recommend that you leave the logs open and then access a table using Impala and monitor it live in the logs, so you will know which filter to use.
... View more