Hello @mrblack  Thank you for reaching out This looks to be a known issue on the old CDH version and is being fixed in CDH 6.3.4 For the time being you can try below two options   1.) As a workaround you can safely increase query monitoring thresholds. In Cloudera Manager > Impala > Configuration > Impala Daemon > Search for "query monitoring": Set "Query Monitoring Timeout" to 30 (Default 5) Set "Query Monitoring Period" to 10 (Default 1) 2.) Try restarting the cloudera-scm-agent as well Note: This does not guarantee that the alerts won't show up again, but will make them less frequent. ... View more

Hello @Hae  Thank you for reaching out on this It looks to be cdp key issue. You can confirm using the below If the below output is returning empty results then we might need to regenerate the same and it would be better to raise a support case to further check this as this will need further debugging >> Run the below command and look for cdp_keys.json # kubectl --kubeconfig ocp-kubeconfig.conf -n cdp get secrets/cm.creds -o yaml >> From the above copy the value of cdp_keys.json and pass below # echo "cdp_key.json" | base64 --decode   ... View more

Hello @steinsgate  Thank you for your update. Glad to know the issue is resolved post-cleanup and reinstallation Yes for the DNS issue as we are discussing on the other thread please check the pre-reqs document and let us know how it goes Let us know if we can mark this as resolved now ... View more

Hello @Juanes  Thank you for reaching out on this Can you please confirm what OS version are you using? Check the output of the following command and see if hostname is the correct one # hostname -f If hostname -f is not returning the complete FQDN then please set the FQDN correct and restart the cloudera-scm-agent and you should be good You might want to check the below discussion https://community.cloudera.com/t5/Support-Questions/The-hostname-and-canonical-name-for-this-host-are-not/m-p/19444 ... View more

Hello @steinsgate  Thank you for your update Yes please ensure that the DNS configuration is correct on the nodes. I mean to say that it should adhere to our documentation. Also, try resolving the hostname manually using nslookup from the nodes and compare the output from the working nodes and see if that works ... View more