i used this github as an example: https://github.com/kerberizer/zkcopy but, without success, it returns the error that was described. ... View more

hi @Zainers , you must specify the class name according to the JDBC driver (.jar) version you are using. remember that the jar must be accessible by all hosts in the NiFi cluster. ... View more

hi @Zainers  perfect! if you already have an open case with the support team, the team will get back to you shortly with a specific solution. 😉   ... View more

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

hi @huimin, perfect! if you could describe the solution you implemented, it will help others who encounter the same issue. hugs. ... View more

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

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

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

@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