You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2009/07/29 03:01:15 UTC

[jira] Resolved: (HBASE-1718) Reuse of KeyValue during log replay could cause the wrong data to be used

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

Jonathan Gray resolved HBASE-1718.
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed.  Upon further thought, this _could_ create cross-family scenario we've seen in HBASE-1638 / HBASE-1715 (but apurtell says no replay).  It does, however, seem to be the case that this bug completely broke log replay as you would always end up only having the last seen KV.

> Reuse of KeyValue during log replay could cause the wrong data to be used
> -------------------------------------------------------------------------
>
>                 Key: HBASE-1718
>                 URL: https://issues.apache.org/jira/browse/HBASE-1718
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1718-v1.patch
>
>
> Our meta table got a row key of METAROW in it.  Hard to explain how it happened, but under code inspection stack found that we are reusing the same KV instance for each replayed key.

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