[
https://issues.apache.org/jira/browse/HBASE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609433#action_12609433
]
stack commented on HBASE-288:
-----------------------------
Joonbok: I thought this patch had already been applied (to hbase since 0.1 and
the hadoop portion to hadoop since 0.16.x?) Is that why its not applying
(Could be hard to figure it because a lot has changed in hbase since 02/07/08).
> Add in-memory caching of data
> -----------------------------
>
> Key: HBASE-288
> URL: https://issues.apache.org/jira/browse/HBASE-288
> Project: Hadoop HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Jim Kellerman
> Assignee: Tom White
> Priority: Trivial
> Fix For: 0.2.0
>
> 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-v7.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.
