Member since 
    
	
		
		
		02-07-2022
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                258
            
            
                Posts
            
        
                61
            
            
                Kudos Received
            
        
                36
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 298 | 10-18-2025 09:09 PM | |
| 299 | 10-02-2025 02:18 AM | |
| 339 | 10-01-2025 05:22 AM | |
| 1656 | 07-30-2025 09:33 PM | |
| 624 | 07-15-2025 07:28 PM | 
			
    
	
		
		
		04-10-2024
	
		
		10:28 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hello @Santy18   Thank you for reaching out.  Could you please confirm the below     >> What version of CM CDP are you using?  >> Is this a new installation or was it running fine for long time?  >> What error do you see in Atlas application logs? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-10-2024
	
		
		12:39 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 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
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-08-2024
	
		
		10:34 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 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
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-08-2024
	
		
		10:19 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 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
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-07-2024
	
		
		09:26 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 Hello @steinsgate   Thank you for reaching out to the community  Can you please confirm the ECS version you are using along with the CM and CDP versions?  Also, are the Kubernetes core pods running? Have all the prerequisites met as per the documentation  # kubectl get pods -n kube-system    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-07-2024
	
		
		08:49 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hello @Rafe   Thank you for reaching out  Can you please elaborate more on your query?  In general yes you can run CDP public cloud as mentioned in the below document     https://docs.cloudera.com/cdp-public-cloud/cloud/requirements-aws/topics/mc-requirements-aws.html 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-07-2024
	
		
		09:30 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hello,  Thank you for your update  Can you please elaborate more on nslookup not working? Do you mean nslookup command is not available or the command is not returning any output?     There is no mandate to have an external DNS server, the entries in /etc/hosts should be enough. What about hostname -f is it working?    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-06-2024
	
		
		10:25 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 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
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-03-2024
	
		
		05:55 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 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
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-03-2024
	
		
		05:51 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello @Juanes   Yes agreed we will need to find out why that URL was wrong  Anyways glad to know that the issue is resolved 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













