hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liyin Tang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6858) Fix the incorrect BADVERSION checking in the recoverable zookeeper
Date Fri, 21 Sep 2012 23:46:07 GMT

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

Liyin Tang commented on HBASE-6858:
-----------------------------------

The recoverable zk tried to recover from the connection less exception gracefully at beginning
and I still believe this problem shall be solved by the zookeeper client library instead of
the application such as HBase. The third option shall be check whether the latest zookeeper
has supported to be recovered by the connection loss exception gracefully. In that case, we
just need to totally remove the recoverable zk !


                
> 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
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6858.patch, HBASE-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