hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-674) memcache size unreliable
Date Fri, 04 Jul 2008 03:14:34 GMT

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

Jim Kellerman updated HBASE-674:

    Attachment: patch.txt

Memcache.add now computes the delta size of the memcache (so if multiple updates are made
to the same row/column/timestamp, they are correctly accounted for)

HStore.add returns the value from Memcache.add

HRegion.internalFlushCache now zeros the memcache size while it has updates locked out. Because
of this, the memcache size will reflect the size of the updates that happened since the flush
started. Additionally, at the end of a cache flush it reports the number of bytes flushed
and not the number of bytes currently in the memcache.

memcache size is now updated based on the value returned from HStore.add (which is computed
by Memcache.add

> 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: Jim Kellerman
>             Fix For: 0.2.0
>         Attachments: 674-v2.patch, 674.patch, patch.txt
> 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.

View raw message