hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2476) HLog sequence number is obtained outside updateLock
Date Tue, 27 Apr 2010 04:07:32 GMT

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

stack updated HBASE-2476:
-------------------------

           Status: Resolved  (was: Patch Available)
     Hadoop Flags: [Reviewed]
    Fix Version/s: 0.20.5
       Resolution: Fixed

Committed to branch (HBASE-1393 fixed this on TRUNK).  Thanks for the patch Todd.

> HLog sequence number is obtained outside updateLock
> ---------------------------------------------------
>
>                 Key: HBASE-2476
>                 URL: https://issues.apache.org/jira/browse/HBASE-2476
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.5
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.20.5
>
>         Attachments: hbase-2476.txt
>
>
> In one of the overloads of HLog.append, obtainSeqNum() is called before this.updateLock
is acquired. This means that it's possible for some other thread to have a higher sequence
number but achieve its write first, and hence the lastSeqWritten map can become incorrect.

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