Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.2.0
    • Component/s: regionserver
    • Labels:
      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

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

        Issue Links

          Activity

            People

            • Assignee:
              Tom White
              Reporter:
              Jim Kellerman
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development