About hxn

hxn · ‎05-10-2022

Hi, I am unable to start cloudera management services. The "Continue" button is enabled and all the nodes are added in cloudera manager as shown in ss below. I haven't created the cluster yet and haven't distributed the parcels aswell. I face the same issue when I try to create cluster it does not move forward even the continue button is enabled as seen in screenshot below: Kindly help me resolve the issue. Regards

hxn · ‎12-02-2021

There is also an option of "Supported TLS versions" in Cloudera Manager under Security, search for SSL you will get the option of "Supported TLS versions" even after selecting TLSv1.2 from that option our security scans show that few ports from impala and some other services are open. Screenshot of Cloudera Manager is attached. Regards Hxn

hxn · ‎11-17-2021

Hi, I have installed CDP 7.1 on my servers. I have enabled autoTLS on those machines during installation. Now my cluster is perfectly up and running. Now for security purpose I want to disable TLS version 1.0 and 1.1 on these machines. In config.ini file which is located in /etc/config.ini minimum tls protocol parameter is set to TLSv1.2 i.e use_tls= 1 minimum_tls_protocol=TLSv1.2 My cloudera manager UI is running at port 7183. According to cloudera official documentation (link: https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/release-guide/topics/cdpdc-networking-security-requirements.html) port 7183 only supports TLSv1.2 as shown in screenshot below: But whenever I try to make connection to this port via TLSv1 it connects successfully. I am using following command to test connectivity: openssl s_client -connect ip:7183 -tls1 Kindly help me resolve this issue. Regards @smruti @GangWar

hxn · ‎10-20-2021

not working...actually kerberos is not enabled on our cluster....only autoTLS is configured.

hxn · ‎10-13-2021

Hi Im using CDP 7.1 and I am unable to make a jdbc connection with impala from a java application using Cloudera_ImpalaJDBC3_2.5.5.1007.Following is the list of drivers shown in screenshot: We are are using Auto TLS provided by cloudera with no kerberos authentication. The connection string which we are using on the node where our impala daemon is runnning using Hiveserver2 port 21050: ConnectionURL = "jdbc:impala://mstl005:21050;AuthMech=4;SSLKeyStore=/var/lib/cloudera-scm-agent/agent-cert/cm-auto-host_keystore.jks;SSLKeyStorePwd=/var/lib/cloudera-scm-agent/agent-cert/cm-auto-host_key.pw;UID=impala;PWD=impala"; We are using AutoTLS .It is throwing me the following error: ConnectionURL = "jdbc:impala://mstl005:21050; this connection string works fine with the mentioned JDBC driver on our other server with no tls enabled. Thanks

hxn · ‎10-07-2021

Do I need to stop I hive and only use hive on tez..? There are 2 hiveserver2 1 is of hive service and the other one is hive on tez's hiveserver2. I am getting following logs on hive on tez's hiveserver2: [shutdown-hook-0]: Error stopping schq java.lang.IllegalStateException: The current ScheduledQueryExecutionService INSTANCE is invalid at org.apache.hadoop.hive.ql.scheduled.ScheduledQueryExecutionService.close(ScheduledQueryExecutionService.java:312) ~[hive-exec-3.1.3000.7.1.7.0-551.jar:3.1.3000.7.1.7.0-551] at org.apache.hive.service.server.HiveServer2.stop(HiveServer2.java:892) ~[hive-service-3.1.3000.7.1.7.0-551.jar:3.1.3000.7.1.7.0-551] at org.apache.hive.service.server.HiveServer2.lambda$init$0(HiveServer2.java:439) ~[hive-service-3.1.3000.7.1.7.0-551.jar:3.1.3000.7.1.7.0-551] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_232] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_232] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_232] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232] @smruti

hxn · ‎10-07-2021

Hi I have installed CDP with CDH 7.1 on my servers. We want to integrate our hue with hive. Earlier it used to show "Error loading databases" after that we uncommented following portion under interpreters section of notebook section in /etc/hue/conf/hue.ini file: [[[mysql]]] name = MySQL interface=sqlalchemy ## https://docs.sqlalchemy.org/en/latest/dialects/mysql.html options='{"url": "mysql://hue:mypassword@myhostnameonwhichhuedbwascreatedandhueserviceisrunning:3306/hue"}' # ## options='{"url": "mysql://${USER}:${PASSWORD}@localhost:3306/hue"}' [[[hive]]] name=Hive interface=hiveserver2 it started showing the databases after making above configurations but its not showing me tables and giving me the following error as shown in below screenshot: 'NoneType' object has no attribute 'settimeout' Hue db was created during installation by following this link, I gave path of this db in above config file: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/install_cm_mariadb.html Both Hive and Hive on Tez are configured in my cluster but HiveServer2 of Hive on Tez is down showing the following error: Error stopping schq Please help me solve these issues and connect hive with hue. Regards

Online	Offline
Last Visited	‎01-13-2023 12:24 AM

Member Since	‎10-06-2021 10:36 PM
Last Visited	‎01-13-2023 12:24 AM
Posts	7

Cloudera Community

Continue button not working

Re: Enforce TLSv1.2 for CDP working with AutoTLS

Enforce TLSv1.2 for CDP working with AutoTLS

Re: Unable to make a jdbc connection with impala

Unable to make a jdbc connection with impala

Re: Unable to Connect Hive with Hue in CDH7.1

Unable to Connect Hive with Hue in CDH7.1