Hello @Riyadbank  Thank you for reaching out to the community   1.) First thing: You can consider increasing the heap memory for CM server in /etc/default/cloudera-scm-server file and restart the cloudera-scm-server 2025-01-10 11:03:00,658 WARN JvmPauseMonitor:com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 26866ms: GC pool 'ParNew' had collection(s): count=1 time=0ms, GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=26804ms 2.) Regarding the actual issue Are the hosts heartbeating fine? Do you see any error in the stderr logs for those individual services?     ... View more

Hello @Lavenda  Thank you for reaching out to community Can you please confirm what is the heap assigned to CM server? You can check the same in /etc/default/cloudera-scm-server Also, do you see JVM pauses in /var/log/cloudera-scm-server/cloudera-scm-server.log.   If you see JVM pauses in the above logs try increasing the heap for CM server and restart the cloudera-scm-server service (systemctl restart cloudera-scm-server)   # cat /var/log/cloudera-scm-server/cloudera-scm-server.log | grep -i "Detected pause in JVM"   ... View more

Hello @Riyadbank  Thank you for reaching out to community Problem 1: conflicting requests - nothing provides module(perl:5.26) needed by module perl-DBD-SQLite:1.58:8080020231031074729:073fa5fe-0.x86_64   The above error indicates that perl module is missing please enabled the repositories for RHEL 8 app stream and base os and try to install the perl module and that should fix your issue  ... View more

Hello @sayebogbon  Apologies for the delayed response It seems the encryptions types are not matching in the keytab and KDC server   I would suggest the below   1.) Stop the cluster through CM 2.) Go to CM --> Administration --> Kerberos --> 'Kerberos Encryption Types', then add the following encryption types: rc4-hmac aes256-cts aes128-cts 3.) Do redeploy krb5.conf through CM,  4.) Regenerate the keytabs and principles from CM UI 5.) Start the cluster Let us know how it goes   ... View more

Hello, Thank you for reaching out Can you please share the error screenshot? Do you see the host on CM UI? Can you compare the /etc/cloudera-scm-agent/config.ini from the working node it that correct? Also share the output of following command   # /opt/cloudera/cm-agent/bin/supervisorctl -c /var/run/cloudera-scm-agent/supervisor/supervisord.conf status     ... View more

Hello @sayebogbon  Thank you for reaching out Can you please confirm if the nodes are heartbeating fine? You can check from Hosts >> All hosts page on CM UI and check the heartbeat Regarding the kerberos errors Can you please login to the node command line and try manual kinit # cd /var/run/cloudera-scm-agent/process Go into latest HDFS process directory and try manual kinit Compare /etc/krb5.conf from working nodes as well Also, has OS upgrade been performed as well?       ... View more

Hello @Hydg  Check the environment pod logs as well Also check the pod logs of pod-cdp-release-thunderhead-environment-7-<replace-me>-thunderhead-environment ... View more

Hello @Hydg  Thanks for reaching out  May be you can try checking the CM server logs ( /var/log/cloudera-scm-server/cloudera-scm-server.log)   Also check the pod logs of pod-cdp-release-thunderhead-environment-7-<replace-me>-thunderhead-environment     ... View more

Hello @Israr  Thank you for reaching out to the community Please refer the following answer and check if that helps   https://community.cloudera.com/t5/Support-Questions/Grafana-support-in-CDP-data/m-p/357186#M237498 https://grafana.com/grafana/plugins/foursquare-clouderamanager-datasource/ ... View more

Hello @Tung  Thank you for reaching out. This seems to be coming from the namenode Please expand the task there you will be able to see more errors FINISHED, success:false, msg:Failed to format NameNode   ... View more