Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 29366 invoked from network); 21 May 2007 18:28:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 18:28:38 -0000 Received: (qmail 57301 invoked by uid 500); 21 May 2007 18:28:42 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 57282 invoked by uid 500); 21 May 2007 18:28:42 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 57273 invoked by uid 99); 21 May 2007 18:28:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 11:28:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 11:28:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 20C6071403A for ; Mon, 21 May 2007 11:28:16 -0700 (PDT) Message-ID: <28911305.1179772096114.JavaMail.jira@brutus> Date: Mon, 21 May 2007 11:28:16 -0700 (PDT) From: "Jim Kellerman (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-1398) Add in-memory caching of data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Add in-memory caching of data ----------------------------- Key: HADOOP-1398 URL: https://issues.apache.org/jira/browse/HADOOP-1398 Project: Hadoop Issue Type: New Feature Components: contrib/hbase Reporter: Jim Kellerman Priority: Minor 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.