hbase-issues mailing list archives

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

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

stack commented on HBASE-6858:
------------------------------

[~jxiang] Yeah, should be fine.  We write the salt into the znode data but the length is appropriately
adjusted.  Reading the data out, we get the length from the znode data, not via some hardcoding
so should work (we don't even look at the id when we are removing it).  If a problem, we'll
catch it when we try old client against new cluster testing an RC. 
                
> 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
>
>
> 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