[HBASE-288] Add in-memory caching of data

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 0.2.0
• Component/s: regionserver
• Assignee: Thomas White
• Reporter: Jim Kellerman
• Created: 21/May/07 18:27
• Updated: 02/May/13 02:29
• Resolved: 07/Feb/08 17:50

Description

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

Issue Links

• depends upon: HBASE-285 HBase administration
• incorporates: HBASE-80 [hbase] Add a cache of 'hot' cells
• is depended upon by: HADOOP-1399 Provide the ability to cache column data in memory
• is duplicated by: HBASE-344 [hbase] Performance - add a block cache
• is duplicated by: HBASE-362 [Hbase] Caching for read performance
• is related to: HBASE-965 Implement BlockCache using custom LRU/ARC mechanism rather than SoftReferences