hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1718) Reuse of KeyValue during log replay could cause the wrong data to be used
Date Wed, 29 Jul 2009 01:33:14 GMT

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

stack commented on HBASE-1718:
------------------------------

So, at a minimum, this patch fixes replaying of logs:

Below I added logging.  Replay had 17k edits.  Only one was added, the last one.

{code}
....
2009-07-29 01:27:15,274 [regionserver/208.76.44.139:60020.worker] INFO org.apache.hadoop.hbase.regionserver.Store:
ADDED TO RECON CACHE: \x00\x00\x00\x03\x00\x01\x07\x02\x08\x05/info:data/1248830494586/Put/vlen=1000
2009-07-29 01:27:15,274 [regionserver/208.76.44.139:60020.worker] DEBUG org.apache.hadoop.hbase.regionserver.Store:
Applied 17286, skipped 0 because sequence id <= 22830124
2009-07-29 01:27:15,274 [regionserver/208.76.44.139:60020.worker] DEBUG org.apache.hadoop.hbase.regionserver.Store:
flushing reconstructionCache: 1
2009-07-29 01:27:15,274 [regionserver/208.76.44.139:60020.worker] INFO org.apache.hadoop.hbase.regionserver.Store:
DUMP \x00\x00\x00\x03\x00\x01\x07\x02\x08\x05/info:data/1248830494586/Put/vlen=1000
{code}

I thought this was hbase-1483 but that was in splitLog.  This is something else.

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


Mime
View raw message