Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <206174682.1248829275528.JavaMail.jira@brutus>
Date: Tue, 28 Jul 2009 18:01:15 -0700 (PDT)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Assigned: (HBASE-1718) Reuse of KeyValue during log replay
 could cause the wrong data to be used
In-Reply-To: <174888853.1248824834792.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray reassigned HBASE-1718:
------------------------------------

    Assignee: Jonathan Gray

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