hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-288) Add in-memory caching of data
Date Mon, 04 Feb 2008 21:09:09 GMT

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

stack commented on HBASE-288:
-----------------------------

Tom, I backed out the hbase component of this patch temporarily.  Notion is that we get hbase
fixed up over in its new svn home, then we branch.  We want the branch to go against hadoop-0.16.0.
 Once branch is done, we'll put this patch back into hbase TRUNK (With this patch in place,
hbase requires post 0.16.0 hadoop).

> Add in-memory caching of data
> -----------------------------
>
>                 Key: HBASE-288
>                 URL: https://issues.apache.org/jira/browse/HBASE-288
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Jim Kellerman
>            Priority: Trivial
>         Attachments: commons-collections-3.2.jar, hadoop-blockcache-v2.patch, hadoop-blockcache-v3.patch,
hadoop-blockcache-v4.1.patch, hadoop-blockcache-v4.patch, hadoop-blockcache-v5.patch, hadoop-blockcache-v6.patch,
hadoop-blockcache.patch
>
>
> Bigtable provides two in-memory caches: one for row/column data and one for disk block
caches.
> The size of each cache should be configurable, data should be loaded lazily, and the
cache managed by an LRU mechanism.
> One complication of the block cache is that all data is read through a SequenceFile.Reader
which ultimately reads data off of disk via a RPC proxy for ClientProtocol. This would imply
that the block caching would have to be pushed down to either the DFSClient or SequenceFile.Reader

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message