[
https://issues.apache.org/jira/browse/HBASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609707#action_12609707
]
viper799 edited comment on HBASE-674 at 7/1/08 1:59 PM:
-------------------------------------------------------------
I currently run jobs in smaller batches and restart hbase after abotu 20 small
jobs inserting about 500K cells per job on one region server.
If we want to get 2.0 out then this should be a blocker in 2.1
was (Author: viper799):
I currently run jobs in smaller batches and restart hbase after abotu 20
small jobs inserting about 500K cells per job on one region server
> 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
> Attachments: 674-v2.patch, 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.
