Member since 
    
	
		
		
		05-10-2016
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                26
            
            
                Posts
            
        
                10
            
            
                Kudos Received
            
        
                4
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 4949 | 01-09-2019 06:17 PM | |
| 3100 | 12-14-2018 07:49 PM | |
| 1729 | 02-24-2017 02:57 PM | |
| 6694 | 09-13-2016 04:52 PM | 
			
    
	
		
		
		12-20-2019
	
		
		01:15 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I have the following issue with this setup .  .I define Livy service on a Knox topology with authentication provider enabled .   When  I request the Livy session over Knox url  Knox requests  the Livy session with doAs  =  myuser . So far so good. ..   Livy sessions is started with owner=Knox and  proxyuser =myuser..   Problem is when we attempt to post to Livy statements API  over the Knox url.   If we use the Knox url for posting to the running Livy session  Knox will add the doAs=myuser . But now  we get a forbidden response . Basically because the Livy session is owned by Knox we cannot post statement into the session over the Knox url with doAs=myuser . in my setup at least only the Knox user may post a statement  to a Livy session owned by Knox .  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-18-2018
	
		
		12:29 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 The amount of memory needed by Ambari Infra Solr by default is too high due to poor configuration choices. I wrote about what simple changes can be made to make Solr significantly more performant on less heap. We have Solr with less than 4GB of heap holding billions of documents.  https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-05-2018
	
		
		12:10 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 These seems to be bogus replay exception when running solr service.   Changes hadoop-env.sh or solr JVM option with -Dsun.security.krb5.rcache=none should fix the problem.  # # Extra Java runtime options.  Empty by default.
export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true -Dsun.security.krb5.rcache=none ${HADOOP_OPTS}"
 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-03-2017
	
		
		08:58 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Adi Jabkowsky This did the trick! Thank you. Now it works. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		11-04-2016
	
		
		07:24 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Good catch.  Tutorial has been updated to provide more links. 
						
					
					... View more