Member since 
    
	
		
		
		01-20-2014
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                578
            
            
                Posts
            
        
                102
            
            
                Kudos Received
            
        
                94
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 6677 | 10-28-2015 10:28 PM | |
| 3543 | 10-10-2015 08:30 PM | |
| 5638 | 10-10-2015 08:02 PM | |
| 4095 | 10-07-2015 02:38 PM | |
| 2875 | 10-06-2015 01:24 AM | 
			
    
	
		
		
		01-03-2018
	
		
		02:04 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 The simple answer is to open up the ports in a bidirectional manner on all the hosts.  For instance:     on each node in cluster A:  Allow connectivity to 1004 (or 50010 without Kerberos) and 50020 on each datanode in cluster B. As well as 8020 to namenodes in Cluster B.     on each node in cluster B: Allow connectivity to 1004 (or 50010 without Kerberos) and 50020 on each datanode in cluster A. As well as 8020 to namenodes in Cluster A.     However... You are right, where the distcp is executed will determine the source/destination.  Executing distcp on Cluster A will cause a mapreduce job to run on cluster A.  Each datanode will(may) run a task that will connect to the namenode(s) on cluster B for block locations and then datanodes on cluster B for transfer.  I'm not sure if the node the distcp is executed on will need access as well.  So I generally run the distcp on one of the datanodes. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-17-2017
	
		
		12:05 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you for you ansver Gautam Gopalakrishnan. And for your question, Alina Gherman. I also thought it was a problem, when the gateway is always N/A. And tryed to fixed it, but unsuccessfully. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-13-2017
	
		
		01:22 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 It could be the issue with firewall   Solution:      Stop the firewall: > service iptables stop  allow the port you want to connect on the host: > ufw allow [port_number] 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-12-2017
	
		
		02:44 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Apparently, the problem was with the 'repodata' I had. The issue got resolved once I created the new repodata for my install-dir where I had all my install files.     I downloaded and installed 'createrepo' tool first and then ran the following using the tool:     createrepo /home/cloudera/install-files     This created a new repodata dir and the files and after this my installation succeeded without any error.    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-23-2017
	
		
		07:04 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Any update on this topic? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-20-2017
	
		
		05:16 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I would suggest starting a new thread with all the details involved in your specific case.  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-09-2017
	
		
		02:47 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi Gautum,  I have tried this property and it worked. But i have noticed that it only try 4 times, After that process didn't start. Are there any other configurations where i can provide the number of times process should restart?     Regards!  Gaurav Garg 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-26-2017
	
		
		03:22 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @MikeJones,     I'm not sure what you are saying.  Either you have Kerberos authentication enabled in a cluster or you don't.  In order to use BDR HDFS replication, you need to have Kerberos enabled on both clusters or not enabled in both clusters.     For information about how BDR replication supports replicating between clusters in different realms, see:    https://www.cloudera.com/documentation/enterprise/latest/topics/cm_bdr_replication_and_kerberos.html     -Ben 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













