hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6858) Fix the incorrect BADVERSION checking in the recoverable zookeeper
Date Fri, 12 Oct 2012 23:15:03 GMT

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

Jimmy Xiang commented on HBASE-6858:
------------------------------------

It may not happen at the same time.  Suppose one client writes the data.  Quite some time
later, another client can try to write the same data same version again.  That's what I'd
like to prevent.  I am ok not to have the extra one, just want to be cautious. :)
                
> Fix the incorrect BADVERSION checking in the recoverable zookeeper
> ------------------------------------------------------------------
>
>                 Key: HBASE-6858
>                 URL: https://issues.apache.org/jira/browse/HBASE-6858
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6858.patch, HBASE-6858_v2.patch, HBASE-6858_v3.patch, trunk-6858.patch,
trunk-6858_v2.patch
>
>
> Thanks for Stack and Kaka's reporting that there is a bug in the recoverable zookeeper
when handling BADVERSION exception for setData(). It shall compare the ID payload of the data
in zk with its own identifier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message