Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # dev - test value used for HBase block size?


Copy link to this message
-
答复: test value used for HBase block size?
谢良 2013-12-12, 03:27
All the BucketCache, LruBlockCache and DoubleBlockache instances are
singleton(not per cf) in current codebase, and you mentioned block size could be set
per CF. so you should not expect to change the block size in those Cache ctor

Thanks,
________________________________________
发件人: Sergey Shelukhin [[EMAIL PROTECTED]]
发送时间: 2013年12月12日 3:22
收件人: [EMAIL PROTECTED]
主题: Re: test value used for HBase block size?

Ping? I'll file a JIRA
On Tue, Dec 10, 2013 at 3:59 PM, Sergey Shelukhin <[EMAIL PROTECTED]>wrote:

> I have a question...
>
> HStore ctor used by HRegion does: this.cacheConf = new CacheConfig(conf,
> family); which calls CacheConfig.instantiateBlockCache(conf) and creates
> BucketCache, LruBlockCache and DoubleBlockCache depending on config.
> However, BucketCache in ctor, as well as CacheConfig when creating others,
> uses StoreFile.DEFAULT_BLOCKSIZE_SMALL as block size (without getting from
> config or anything).
>
> DEFAULT_BLOCKSIZE_SMALL is described as:
> {code}
>   // Make default block size for StoreFiles 8k while testing.  TODO: FIX!
>   // Need to make it 8k for testing.
>   public static final int DEFAULT_BLOCKSIZE_SMALL = 8 * 1024;
> {code}
>
> Should it be 8k? Am I missing something? It's been like that forever (at
> least the constant, didn't check the usage).
>
>

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.