Hello @kiki_adm  Thank you for reaching to Cloudera Community Regarding the reported behavior where the Pod Count decreased from 54 to 18 after restarting the service, this does not necessarily indicate that pods were actually deleted or that there is an issue with the cluster. The Pod Count displayed on the dashboard represents the number of pods being returned by the underlying monitoring/metrics query for the configured scope and filters. Therefore, the value can temporarily change after a service restart while the monitoring component is rebuilding or reloading its pod information. To determine whether this is an actual pod-level issue or only a monitoring/dashboard discrepancy, we recommend first comparing the dashboard value with the actual Kubernetes pod count. For example: kubectl get pods -A --no-headers | wc -l For a specific namespace: kubectl get pods -n <namespace> --no-headers | wc -l kubectl get pods -n <namespace> It is also useful to check the pod status: kubectl get pods -A If Kubernetes shows that the expected number of pods are running while the dashboard shows only 18, this would indicate that the issue is likely related to metrics collection, monitoring, or the dashboard query, rather than an actual loss of pods. Looking forward for your response ... View more

Hello @s-raju  Thank you for reaching out to Cloudera community Can you please share the exact error with Ranger KMS? Did you tried restarting Ranger KMS? Are there any errors in Ranger KMS logs?  What error are we facing job ? Thank you Kshitij Upadhyay ... View more

Yes delete the file and restart the agent that should help  ... View more

Hello @jkoral  Thank you for reaching out to Cloudera community You mean to say the node is still coming with old hostname even though you changed the hostname So cloudera-agent will work with UUID's as well which is stored in /var/lib/cloudera-scm-agent/uuid  Can you check once if that file is same or different? What UUID host is showing in CM UI?     ... View more

Hello @shubham_rai  Could you please provide an update on this? Was the hive on Tez not restarted, or was a false stale entry present on the hive on Tez? Was a restart required or stale entry icon was gone on its own? Did you find any error in CM server logs? Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. ... View more

Hello @Olivia-donut  Could you please confirm if you are still facing the issue? Is the heartbeat working fine? Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.   ... View more

Hello @Olivia-donut  Thank you for your update Actually, the same document holds true for both scenarios, that is, with TLS as well as without TLS.  Also what about the networking angle? Let's try manual telnet    # telnet <my_load_balancer> 7182 # openssl s_client -connect my_load_balancer:7182   ... View more