You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "samar (JIRA)" <ji...@apache.org> on 2013/05/27 13:09:20 UTC

[jira] [Commented] (HBASE-5024) A thread named LruBlockCache.EvictionThread remains after the shutdown of a cluster

    [ https://issues.apache.org/jira/browse/HBASE-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667695#comment-13667695 ] 

samar commented on HBASE-5024:
------------------------------

Hope i got it right
 
in class HRegionServer 

 if (cacheConfig.isBlockCacheEnabled()) {
      cacheConfig.getBlockCache().shutdown();
    }

LruBlockCache.shutdown has 
{
...
 this.evictionThread.shutdown();

}
which should shutdown the eviction thread.



                
> A thread named LruBlockCache.EvictionThread remains after the shutdown of a cluster
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-5024
>                 URL: https://issues.apache.org/jira/browse/HBASE-5024
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>            Reporter: Nicolas Liochon
>            Priority: Minor
>
> There is no cleanup function in hbase.io.hfile.CacheConfig. The cache is a singleton, shared by all cluster if we launch more than one cluster on a test.
> Related code is:
> {noformat}
>   /**
>    * Static reference to the block cache, or null if no caching should be used
>    * at all.
>    */
>   private static BlockCache globalBlockCache;
>   /** Boolean whether we have disabled the block cache entirely. */
>   private static boolean blockCacheDisabled = false;
>   /**
>    * Returns the block cache or <code>null</code> in case none should be used.
>    *
>    * @param conf  The current configuration.
>    * @return The block cache or <code>null</code>.
>    */
>   private static synchronized BlockCache instantiateBlockCache(){
>      // initiate globalBlockCache
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira