You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/05 18:26:51 UTC
[jira] Commented: (HBASE-3418) Increment operations can break when
qualifiers are split between memstore/snapshot and storefiles
[ https://issues.apache.org/jira/browse/HBASE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977864#action_12977864 ]
Todd Lipcon commented on HBASE-3418:
------------------------------------
Can we put this in 0.90? seems like inaccurate counters are a bad problem!
> Increment operations can break when qualifiers are split between memstore/snapshot and storefiles
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-3418
> URL: https://issues.apache.org/jira/browse/HBASE-3418
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.90.0
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Priority: Critical
> Fix For: 0.90.1, 0.92.0
>
> Attachments: HBASE-3418-v1.patch
>
>
> Doing investigation around some observed resetting counter behavior.
> An optimization was added to check memstore/snapshots first and then check storefiles if not all counters were found. However it looks like this introduced a bug when columns for a given row/family in a single increment operation are spread across memstores and storefiles.
> The results from get operations on both memstores and storefiles are appended together but when processed are expected to be fully sorted. This can lead to invalid results.
> Need to sort the combined result of memstores + storefiles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.