About rki_

rki_ · ‎07-28-2022

Hi, can you check in the Ambari server log and see what error are you getting there.

rki_ · ‎07-28-2022

Hi, Can you check if you have the same repo file on the new host which in there in the old hosts. Check if you are able to install the package from commandline. # yum clean all # yum repolist # yum install -y hive-3-1-0-0-78

rki_ · ‎07-26-2022

Hi @jeromedruais , This CVE will be addressed in CDP 7.1.8. Till then, you can use the below precautions: 1. ensure in the linux sudoers files that there is no entry allowing users or groups to run as the yarn account. 2. ensure the cluster is kerberized 3. ensure the permissions for the yarn keytabs are not readable by others. find /var/run/cloudera-scm-agent/ | grep yarn | grep keytab (by default in kerberized cdp, others can't read these service keytabs)

rki_ · ‎07-26-2022

Hi, Are you able to submit the job using YARN client mode (--deploy-mode client)?

rki_ · ‎07-25-2022

Hi @federicoferruti Have you added yarn gateway on the system from where the command is ran so that it gets the basic configuration to connect to RM. If HA is enabled, do check of you have set yarn.resourcemanager.webapp.address.<rm‐id>.

rki_ · ‎07-25-2022

Hi Hanni, Are you able to view the content from the commndline? When accessing the files from Web Ui, the default user as per hadoop.http.staticuser.user is drwho. So make sure this user has the necessary permissions for the file. As the file has read permission for others, do check the Namenode logs for any warnings. Also, try using a different browser and check if above doesn't help.

rki_ · ‎07-24-2022

Hi @Meepoljd As per the description of the issue, I believe you are hitting ZOOKEEPER-1622 . Cloudera has already released TSB-2022-577 for this. As mentioned in the TSB, the session IDs should be unique but due to this bug, two clients might use the same session ID and hence causing the unexpected session termination.

rki_ · ‎07-22-2022

Hi, A hole in region chain most probably indicates there are some regions which are not yet online and hence creates a hole. # cat hbck.report | grep "not deployed on any region server" If you see regions in the above command output, you will need to assign them using hbase shell.

rki_ · ‎07-22-2022

Hello @loridigia You can try to assign the region from hbase shell. > assign '28dd7c81713c9347e8dfe4e6993b1ec7' If you can attach the below command output (with valid ticket ), we can check which all regions are offiline or in transition. # hbase hbck -details

rki_ · ‎07-21-2022

As per the stack trace, it seems to be an issue with the JDK. Do check HIVE-21237 HIVE-21584

Online	Offline
Last Visited	‎12-19-2024 07:22 AM

Member Since	‎07-30-2020 02:04 AM
Last Visited	‎12-19-2024 07:22 AM
Posts	219
Kudos received	44

Cloudera Community

Re: Restore data from datanode after doing hdfs na...

Re: HBase "Master is initializing" error in pseudo...

Re: After upgrading Cloudera Manager to 7.11.3, Li...

Re: Can HDFS Rebalancer run without interrupted Pr...

Re: CM-HDFS

Re: add hosts for old version

Re: add hosts for old version

Re: CVE-2021-33036

Re: Yarn not connect to resource manager

Re: Yarn not connect to resource manager

Re: Couldn't preview file in hdfs

Re: Zookeeper same seesionId cause Master exceptio...

Re: Dead region servers

Re: Dead region servers

Re: hive installation