Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1948411266.1208810362373.JavaMail.jira@brutus>
Date: Mon, 21 Apr 2008 13:39:22 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-586) HRegion runs HStore memcache
 snapshotting -- fix it so only HStore knows about workings of memcache
In-Reply-To: <26386929.1208391081507.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-586:
------------------------

    Attachment: 586-v3.patch

This version is like v2 but I did more clean up of logging messages adding method to FSUtils that will return a path minus the Filesystem instance qualifier.

> HRegion runs HStore memcache snapshotting -- fix it so only HStore knows about workings of memcache
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-586
>                 URL: https://issues.apache.org/jira/browse/HBASE-586
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.2.0
>
>         Attachments: 586-v2.patch, 586-v3.patch, 586.patch
>
>
> HRegion needs to keep count of memcache sizes.  Currently its trying to run the  memcaches snapshots so it can keep up this number.  HRegion should know nothing about no memcache snapshotting -- should be internal to flushing ... especially since HBASE-532 fix.   HRegion can ask for store sizes....  Add that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.