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] Commented: (HBASE-674) memcache size unreliable
Date Fri, 04 Jul 2008 19:13:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610642#action_12610642
] 

Jim Kellerman commented on HBASE-674:
-------------------------------------

Computing the memcache size is an approximation at best. If the memcache size is not growing
over time, and causing OutOfMemoryExceptions, then I think this the best we can do for 0.2.0.
If you think the accounting should be more accurate, please open an issue for 0.3.0.

> 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.


Mime
View raw message