Member since 
    
	
		
		
		02-01-2016
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                71
            
            
                Posts
            
        
                36
            
            
                Kudos Received
            
        
                5
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 5137 | 06-27-2019 10:09 AM | |
| 1983 | 01-27-2017 05:22 AM | |
| 2321 | 01-06-2017 05:05 AM | |
| 3554 | 11-17-2016 05:37 AM | |
| 3788 | 03-03-2016 12:28 PM | 
			
    
	
		
		
		06-27-2019
	
		
		10:09 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Followed the steps as suggested by @Jay Kumar SenSharma .. backed up hbase rootdir and added the service again in ambari UI. Its working absolutely fine now. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		01:44 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Jay Kumar SenSharma Unfortunately I didn't have the Configs backup to add the same and also currently hbase service is operational and working fine.      If I re-add the same using ADD SERVICE from ambari .. What would be the impact on the running service ? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		01:43 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Jay Kumar SenSharma  I have executed below commands in Postgres DB      delete from hostcomponentstate where service_name = 'HBASE';     delete from hostcomponentdesiredstate where service_name = 'HBASE';     delete from servicecomponentdesiredstate where service_name = 'HBASE';     delete from servicedesiredstate where service_name = 'HBASE';     delete from serviceconfighosts where service_config_id in (select service_config_id from serviceconfig where service_name = 'HBASE');     delete from serviceconfigmapping where service_config_id in (select service_config_id from serviceconfig where service_name = 'HBASE');     delete from serviceconfig where service_name = 'HBASE';     delete from requestresourcefilter where service_name = 'HBASE';     delete from requestoperationlevel where service_name = 'HBASE';     delete from clusterservices where service_name ='HBASE';     delete from clusterconfig where type_name like 'HBASE%';     delete from clusterconfigmapping where type_name like 'HBASE%';     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		10:16 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Neeraj Sabharwal 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		10:09 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Kuldeep Kulkarni 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		10:08 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Jay Kumar SenSharma 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2019
	
		
		07:55 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Due to Amabri "DB configs consistency check failed" .. I have deleted all the service configs of HBASE from ambari DB as suggested in one of the articles https://community.hortonworks.com/questions/69240/ambar-server-start-failes-with-db-configs-consiste.html but after that .. I am able to start ambari server without errors but unable to see hbase service in Amabri UI 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache Ambari
 
			
    
	
		
		
		12-20-2017
	
		
		06:08 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 ShortCircuitCache(0x8671076): failed to release short-circuit shared memory slot Slot(slotIdx=74, shm=DfsClientShm(ad7f9d8145e3cb1e1ea3e42955eacfb5)) by sending ReleaseShortCircuitAccessRequestProto to /var/lib/hadoop-hdfs/dn_socket.  Closing shared memory segment.  java.io.IOException: ERROR_INVALID: there is no shared memory segment registered with shmId ad7f9d8145e3cb1e1ea3e42955eacfb5
	at org.apache.hadoop.hdfs.shortcircuit.ShortCircuitCache$SlotReleaser.run(ShortCircuitCache.java:208)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745) 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-19-2017
	
		
		09:12 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 2017-12-19 02:40:55,536 ERROR [ShortCircuitCache_SlotReleaser] shortcircuit.ShortCircuitCache: ShortCircuitCache(0x79bb282e): failed to release short-circuit shared memory slot Slot(slotIdx=6, shm=DfsClientShm(4c3535b7ecb532cd3bb275306d5b86d5)) by sending ReleaseShortCircuitAccessRequestProto to /var/lib/hadoop-hdfs/dn_socket.  Closing shared memory segment.
java.io.IOException: ERROR_INVALID: there is no shared memory segment registered with shmId 4c3535b7ecb532cd3bb275306d5b86d5 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache HBase
 
			
    
	
		
		
		12-19-2017
	
		
		07:29 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 We had the same scenario in our environment and thanks for the resolution... Its picking LDAP user id and worked perfectly when the userid range has been updated. 
						
					
					... View more