[
https://issues.apache.org/jira/browse/HBASE-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460908#comment-13460908
]
Gregory Chanan commented on HBASE-6858:
---------------------------------------
Let me ask a potentially silly question here...
Why do we just check that the id is the same? This basically says that the
version of the data in ZK was set by the current recoverable ZooKeeper, but
what if the data is different? This seems like an error to me? I.e. if I
called setData with a certain version/data and I didn't get an error, I'd
expect that at least for that version, the data is what I requested. But this
would swallow that error.
> 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
