Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 78123 invoked from network); 9 Jun 2008 22:34:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jun 2008 22:34:05 -0000 Received: (qmail 18435 invoked by uid 500); 9 Jun 2008 22:34:08 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 18408 invoked by uid 500); 9 Jun 2008 22:34:08 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 18397 invoked by uid 99); 9 Jun 2008 22:34:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2008 15:34:08 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2008 22:33:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 13C92234C139 for ; Mon, 9 Jun 2008 15:33:45 -0700 (PDT) Message-ID: <479235246.1213050825080.JavaMail.jira@brutus> Date: Mon, 9 Jun 2008 15:33:45 -0700 (PDT) From: "stack (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Assigned: (HBASE-674) memcache size unreliable In-Reply-To: <452364312.1213044885048.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-674: --------------------------- Assignee: stack > memcache size unreliable > ------------------------ > > Key: HBASE-674 > URL: https://issues.apache.org/jira/browse/HBASE-674 > Project: Hadoop HBase > Issue Type: Bug > Affects Versions: 0.1.2 > Reporter: stack > Assignee: stack > Priority: Blocker > Fix For: 0.2.0 > > Attachments: 674.patch > > > Multiple updates against same row/column/ts will be seen as increments to cache size on insert but when we then play the memcache at flush time, we'll only see the most recent entry and decrement the memcache size by whatever its size; memcache will be off. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.