You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:08:58 UTC
[jira] [Resolved] (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:all-tabpanel ]
stack resolved HBASE-5024.
--------------------------
Resolution: Cannot Reproduce
Don't seem to see this in more modern hbase's. Resolving (Matteo traced code and we should be doing right thing).
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)