[
https://issues.apache.org/jira/browse/HBASE-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475453#comment-13475453
]
Gregory Chanan commented on HBASE-6858:
---------------------------------------
Whose semantics are we talking about? I assume you mean ZK. We can have our
own semantics for what repeated writes to ZK mean and handle it at this layer.
That doesn't necessarily mean ignore BADVERSIONS if the data is the same, it
could mean rethrowing the BADVERSION.
bq. Very likely, the client(s) is trying to doing something it thinks only it's
doing. It could be done many times, which is ok.
bq. If it should be done only once, then it is a problem.
Where would this cause a problem? If the data is different, we'll throw an
error. Will we miss an expected zk dataChanged call or something?
> 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,
> trunk-6858_v3.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
