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 2010/04/15 21:30:49 UTC
[jira] Updated: (HBASE-2451) .META. by-passes cache;
BLOCKCACHE=>'false'
[ https://issues.apache.org/jira/browse/HBASE-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-2451:
-------------------------
Attachment: meta.txt
Testing this patch now. I see LruCache actually doing something now on the HRS carrying .META. Will let it run a while.
> .META. by-passes cache; BLOCKCACHE=>'false'
> -------------------------------------------
>
> Key: HBASE-2451
> URL: https://issues.apache.org/jira/browse/HBASE-2451
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.20.4, 0.20.5, 0.21.0
>
> Attachments: meta.txt
>
>
> In a new install, if I describe '.META.', it says:
> {code}
> DESCRIPTION ENABLED
> {NAME => '.META.', IS_META => 'true', MEMSTORE_FLUSHSIZE => '16384', F true
> AMILIES => [{NAME => 'historian', COMPRESSION => 'NONE', VERSIONS => '
> 2147483647', TTL => '604800', BLOCKSIZE => '8192', IN_MEMORY => 'false
> ', BLOCKCACHE => 'false'}, {NAME => 'info', COMPRESSION => 'NONE', VER
> SIONS => '10', TTL => '2147483647', BLOCKSIZE => '8192', IN_MEMORY =>
> 'false', BLOCKCACHE => 'true'}]}
> {code}
> BLOCKCACHE is 'true' for the 'info' family (Yes historian is still in 0.20 branch).
> But, if I add logging to hfile and storefile and store, blockcache is 'false' -- there is no cache constructed for use by the hfile.
> This is killing cluster performance.
> It looks like a problem parsing the 'true' value in columnfamily. I'll put up a patch in the morning. Meantime, marking as blocker on 0.20.4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira