Member since 
    
	
		
		
		05-28-2015
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                12
            
            
                Posts
            
        
                1
            
            
                Kudos Received
            
        
                0
            
            
                Solutions
            
        
			
    
	
		
		
		02-01-2019
	
		
		03:27 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @jmedel how did fix this issue? I face the same issue now... 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-18-2016
	
		
		02:06 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 We met Namenode slow issue, and found two ticket, and said release in hadoop 2.8
and I tried hdp2.5 pre, found hadoop version is 2.7.1,
So we want to apply the patches to hdp2.4.2, is that possible?  https://issues.apache.org/jira/browse/HDFS-7858    patch -R -p1 < /mnt/tmp/HDFS-7858.13.patch 
patching file hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/MultiException.java
patching file hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryInvocationHandler.java
Hunk #1 succeeded at 23 with fuzz 2.
Hunk #2 FAILED at 101.
Hunk #3 succeeded at 115 (offset 5 lines).
Hunk #4 succeeded at 131 (offset 5 lines).
Hunk #5 succeeded at 140 (offset 5 lines).
Hunk #6 succeeded at 174 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryInvocationHandler.java.rej
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/ConfiguredFailoverProxyProvider.java
Hunk #2 succeeded at 39 (offset 1 line).
Hunk #3 succeeded at 52 (offset 1 line).
Hunk #4 succeeded at 79 with fuzz 2 (offset 1 line).
Hunk #5 succeeded at 103 (offset 1 line).
Hunk #6 succeeded at 121 (offset 1 line).
Hunk #7 succeeded at 132 (offset 1 line).
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/RequestHedgingProxyProvider.java
Unreversed patch detected!  Ignore -R? [n] y
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/RequestHedgingProxyProvider.java.rej
patching file hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSHighAvailabilityWithNFS.md
Hunk #1 succeeded at 189 (offset -6 lines).
patching file hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSHighAvailabilityWithQJM.md
Hunk #1 succeeded at 208 (offset -8 lines).
patching file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestRequestHedgingProxyProvider.java
Unreversed patch detected!  Ignore -R? [n] y
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestRequestHedgingProxyProvider.java.rej
 https://issues.apache.org/jira/browse/HDFS-6763
 patch -p1 < /mnt/tmp/HDFS-6763.v3.patch 
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/BackupImage.java
Reversed (or previously applied) patch detected!  Assume -R? [n] y
Hunk #1 succeeded at 25 (offset 1 line).
Hunk #2 succeeded at 93 (offset -1 lines).
Hunk #3 FAILED at 222.
1 out of 3 hunks FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/BackupImage.java.rej
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java
Hunk #1 succeeded at 64 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 77 (offset 7 lines).
Hunk #3 succeeded at 148 (offset 6 lines).
Hunk #4 succeeded at 320 (offset 3 lines).
Hunk #5 succeeded at 659 (offset 147 lines).
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
Reversed (or previously applied) patch detected!  Assume -R? [n] y
Hunk #2 FAILED at 42.
Hunk #3 FAILED at 59.
Hunk #4 FAILED at 67.
Hunk #5 FAILED at 142.
Hunk #6 FAILED at 843.
5 out of 6 hunks FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java.rej
patching file hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
Hunk #1 succeeded at 1135 (offset 16 lines).
patching file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestDiskspaceQuotaUpdate.java
Hunk #1 FAILED at 339.
1 out of 1 hunk FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestDiskspaceQuotaUpdate.java.rej
patching file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSImageWithSnapshot.java
Hunk #1 FAILED at 158.
1 out of 1 hunk FAILED -- saving rejects to file hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSImageWithSnapshot.java.rej
  
Or Anything wrong?
 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
- 
						
							
		
			Apache Hadoop
			
    
	
		
		
		04-14-2016
	
		
		11:30 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I started 20 balancers before, yes, off icier document said only one, but I check the source code,  the comment said you cannot start multiple processes to do the balance, but the code is not finished. and the speed is very fast!  I am not sure the fatal disadvantage of start multiple balancers. Maybe the network, IO or something else. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-14-2016
	
		
		11:23 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I think in the large cluster, we need to scale-out datanode everyday, and add new datanode day by day, so we keep running balancer all time.  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		04-14-2016
	
		
		11:09 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 for default your are using dr.who to open the page, bu dr.who don't have the permission. you can check "hadoop.http.staticuser.user" in core-site.xml 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-08-2015
	
		
		11:08 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 hi, ttruong     Just resolved this problem.  when I run MR job on my datanode(hadoop server), I can see the page, but when I run on client side, it cannot.  So I think there should be something diff between server side and client side.  I found my client config file missed "yarn.resourcemanager.webapp.address" property.  When I added it in yarn-site.xml on client side:  <property>    <name>yarn.resourcemanager.webapp.address</name>    <value>$HOSTNAME:8088</value>  </property>     It works fine!!  Hope can help you.  good luck!     Linou    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-28-2015
	
		
		06:07 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 hello ttruong,     I had the same issue with you one month ago, but it was fixed by some operation(I did so many operations, I did not know which one fixed it).  And for the sevral weeks it worked fine. But yesterday, it didn't work any more, but I didn't do anything...  I guess it is something wrong with which permission of the log directory...     keep in touch     Linou 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-28-2015
	
		
		03:21 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi, ttruong, did you found how to fix this error?    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        






