Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-288

Add in-memory caching of data

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • None
    • 0.2.0
    • regionserver
    • None

    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

      Attachments

        1. hadoop-blockcache.patch
          21 kB
          Thomas White
        2. hadoop-blockcache-v2.patch
          22 kB
          Thomas White
        3. hadoop-blockcache-v3.patch
          38 kB
          Thomas White
        4. commons-collections-3.2.jar
          558 kB
          Thomas White
        5. hadoop-blockcache-v4.patch
          78 kB
          Thomas White
        6. hadoop-blockcache-v4.1.patch
          82 kB
          Thomas White
        7. hadoop-blockcache-v5.patch
          82 kB
          Thomas White
        8. hadoop-blockcache-v6.patch
          82 kB
          Thomas White
        9. hadoop-blockcache-v7.patch
          72 kB
          Thomas White

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tomwhite Thomas White
            jimk Jim Kellerman
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment