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 19:58:54 UTC
[jira] Commented: (HBASE-2451) .META. by-passes cache;
BLOCKCACHE=>'false'
[ https://issues.apache.org/jira/browse/HBASE-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857442#action_12857442 ]
stack commented on HBASE-2451:
------------------------------
I'm currently trying to figure why this is the case:
{code}
hbase(main):001:0> scan '-ROOT-'
2010-04-15T10:54:17.901-0700: 8.334: [GC 8.334: [ParNew: 19136K->2112K(19136K), 0.0270080 secs] 24761K->10598K(83008K), 0.0270680 secs] [Times: user=0.13 sys=0.04, real=0.03 secs]
ROW COLUMN+CELL
.META.,,1 column=info:regioninfo, timestamp=1271352114030, value=REGION => {NAME => '.META.
,,1', STARTKEY => '', ENDKEY => '', ENCODED => 1028785192, TABLE => {{NAME => '.M
ETA.', IS_META => 'true', MEMSTORE_FLUSHSIZE => '16384', FAMILIES => [{NAME => 'h
istorian', VERSIONS => '2147483647', COMPRESSION => 'NONE', TTL => '604800', BLOC
KSIZE => '8192', IN_MEMORY => 'false', BLOCKCACHE => 'false'}, {NAME => 'info', V
ERSIONS => '10', COMPRESSION => 'NONE', TTL => '2147483647', BLOCKSIZE => '8192',
IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}}
.META.,,1 column=info:server, timestamp=1271352175741, value=10.20.20.189:60020
.META.,,1 column=info:serverstartcode, timestamp=1271352175741, value=1271352174642
1 row(s) in 0.0930 seconds
hbase(main):002:0> describe '.META.'
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}
i.e. if you scan -ROOT-, it has BLOCKCACHE false for the .META. region but if I describe it, then its 'true'.
> .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
>
>
> 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