Member since 
    
	
		
		
		05-20-2020
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                125
            
            
                Posts
            
        
                6
            
            
                Kudos Received
            
        
                6
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 2682 | 10-25-2021 01:17 AM | |
| 4043 | 10-18-2021 07:13 AM | |
| 5479 | 10-03-2021 11:54 PM | |
| 1379 | 07-11-2021 01:21 PM | |
| 15594 | 04-19-2021 02:50 AM | 
			
    
	
		
		
		01-09-2022
	
		
		02:23 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 You can rename the alias, but you will have to do a cleanup of internal topics to avoid confusion.  It will be like a new replication (it wont work as a rename and re-initiate from the same point.)  Please refer to the below article for the same.   https://community.cloudera.com/t5/Customer/SRM-Internal-Topics/ta-p/328811 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-14-2021
	
		
		04:08 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Couple of possibilities for this WARN messages are:  1) If there is any GC issue on the datanode, this type of WARN messages is seen.  2) If there is any disk issue  3) the last possibility is network latency/slowness between the application, Kafka node, and datanode. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-02-2021
	
		
		05:11 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello,     This timeout exceptions relates to CM Metrics Store (firehose) being overloaded.  Please review the below article - https://community.cloudera.com/t5/Customer/How-to-enable-the-entity-summary-servlet-in-Cloudera-Manager/ta-p/294697       Check KAFKA_PRODUCER and KAFKA_CONSUMER, if we have too many entities (millions), this might cause SMON to request a lot of memory to process the metrics causing timeout exceptions in the SMM server.    To avoid a huge amount of entities that will cause issues with services like SMON, use a client.id in your producers, from the consumer point of view, use a group.id to avoid creating random ids every time a client is executed.      Alternatively Resetting/deleting the Firehose LevelDB storage could be an option to recover from this.       If the SMM server is getting timeout exceptions, check the SMM heap size, it’s recommended (depending on the number of resources we are monitoring) to increase this, acceptable values for production environments are between 8~16GB for SMM.   
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-26-2021
	
		
		09:46 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Depends on your brokers  version to support, as the error says.  Related KIP-133 (implemented in Kafka 0.11, according to JIRA) 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-25-2021
	
		
		01:17 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hello @roshanbi       JSON is one of the best data exchange format  which is lightweight and compact. C/DSV can be used when large dataset, with bandwidth limits are to be sent, but DSV cannot be used where the data is complex and unstructured; there comes in JSON.     So, as you said, you are are seeing a better performance with DSV, that is because it does not contain attribute-value pair as in JSON (which makes it structured). To fine tune you application, you can use   Compression. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-18-2021
	
		
		07:13 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Yes, there has to be a corresponding user in Ranger to authorise, it can not be just a certificate.   You can use Kafka SSL Authentication by setting it up for 2 way   https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/kafka-securing/topics/kafka-secure-auth-tls-broker.html  and if you want Authorisation(via Ranger) add the user  https://docs.cloudera.com/runtime/7.2.8/security-ranger-authorization/topics/security-ranger-users-groups-permissions.html     The same is also discussed here - https://cwiki.apache.org/confluence/display/KAFKA/KIP-371%3A+Add+a+configuration+to+build+custom+SSL+principal+name     Hope this helps.  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-18-2021
	
		
		04:05 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello    Is this during Kafka start or Kafka Mirror Maker start?  What if you try to pass the values in   "Kafka Broker Advanced Configuration Snippet (Safety Valve) for ssl.properties" to pass the properties (ssl.keystore.password, ssl.key.password and ssl.truststore.password. i.e, without .generator)?  Kafka MirrorMaker has a known issue: .generator properties do not work for producer configs.  This affects CDK 3.X (CDH 6.X contains a fix for this issue from 6.2). - CDH-73094      Which version are you using? Please specify both CM and CDH version.   This can cause issue too if they are not compatible.      Is this an upgrade cluster or new?    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-05-2021
	
		
		09:29 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I believe the user "some_user" exists but not the   'OU=Dept,O=Company,C=DE,ST=Germany,CN=some_user'  You should configure ssl.principal.mapping.rules to skip these warnings.  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-03-2021
	
		
		11:54 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello @DA-Ka      The data might be skewed in one of the disks because some of the heavily used topics/partitions are in that particular disk.      You may want to profile the data residing (sort the kafka logs.dir) and reassign them to the other disk using the partition reassignment tool kafka-reassign-partition.sh or manually.         du -sh /kafka-logs/*          
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-11-2021
	
		
		10:18 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 https://www.youtube.com/watch?v=UrX2RWM2vQQ 
						
					
					... View more