Member since 
    
	
		
		
		09-23-2015
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                44
            
            
                Posts
            
        
                49
            
            
                Kudos Received
            
        
                18
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 3112 | 02-08-2017 03:44 PM | |
| 3908 | 02-06-2017 11:03 PM | |
| 4214 | 12-20-2016 02:06 AM | |
| 2021 | 04-29-2016 01:56 PM | |
| 2097 | 04-07-2016 03:11 AM | 
			
    
	
		
		
		12-29-2015
	
		
		05:25 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 NFS_GATEWAY is defined only in HDP-2.3 but from the logs it looks like its being expected in HDP-2.2. Can you check the DB and check that the cluster is indeed at HDP-2.3 - see tables "stack", "clusters" and "clusterstate". Which version of Ambari are you using and how did you perform the upgrade from HDP-2.2 to HDP-2.3 - manual, or rolling? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-26-2015
	
		
		12:06 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 What version of HDP are you deploying? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-23-2015
	
		
		11:28 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							@Hassan Faouaz  the ambari-server log (/var/log/ambari-server/ambari-server.log) should have some more details. Can you share that? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		11-09-2015
	
		
		02:49 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I am not aware of any known issues - although I have not seen any such deployment. On the other hand, I think, Windows deployment of hadoop uses the same user for all services.. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-22-2015
	
		
		04:44 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 From Ambari perspective, if you stop HDFS, modify the config property shown below, move all content to the new location it will likely work.  Someone from HDFS team can confirm if there is any affinity to the actual folder path.  <property>
      <name>dfs.namenode.checkpoint.dir</name>
      <value>/hadoop/hdfs/namesecondary</value>
</property>
 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-22-2015
	
		
		04:19 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 The location of Slider client is immaterial. Slider client just gets used to submit the Yarn App running HBase. All it needs is access to the HBase App package. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-22-2015
	
		
		02:54 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 Not really. We are working on integrating StackAdvisor capability to blueprint based deployment in the next release. That will automatically modify the given blueprint to set correct defaults. Kafka team may have some recommendations. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-30-2015
	
		
		04:46 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 Yes you can use APIs. Sample:  A PUT call at http://ambari.host:8080/api/v1/clusters/c1/config_groups/2  with payload:  [{"ConfigGroup":{"id":2,"cluster_name":"c1","group_name":"A config group","tag":"HDFS","description":"A config group","hosts":[{"host_name":"host1"}],"service_config_version_note":"change","desired_configs":[{"type":"hdfs-site","tag":"version1443587493807","properties":{"dfs.replication":"2","dfs.datanode.du.reserved":"1073741822"}}]}}]   will modify the config group. A POST to http://ambari.host:8080/api/v1/clusters/c1/config_groups would have created a new config group. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-29-2015
	
		
		01:31 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 There is no inherent support. What I described is what some users have implemented. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-29-2015
	
		
		01:30 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		6 Kudos
		
	
				
		
	
		
					
							 High availability for Ambari Server can be achieved by enabling a rapid failover mechanism (an active-passive setup) through an external monitoring tool e.g. Upstart, Supervisor or some other Daemon tool.  Customers deploys two (2) Ambari servers configured exactly same having same Ambari property files. One of the server is kept active while the other is stopped.   The responsibilities of the external monitoring service are:  
 Ensure there is only one active instance of Ambari Server  Monitor the active instance and if it’s down then make a decision to either bring the same instance back up or the replacement instance  Ensure that the agents are re-configured to communicate with the active Ambari Server instance   Requirements for HA   The Ambari DB must be an external DB instance (do not use embedded postgres)  Both Ambari Server instances must be configured similarly (options available via ambari-server setup command)  Appropriate load-balancer setup to route client requests to the active Ambari Server instance  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		- « Previous
- Next »
 
        











