[
https://issues.apache.org/jira/browse/HBASE-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256889#comment-13256889
]
stack commented on HBASE-5790:
------------------------------
@Ted Its not a runtime requirement that client or ensemble be 3.4.x. 3.4.x
client and ensemble is required if you run secure hbase else its not necessary
and we should be wary requiring it; e.g. our ops didn't want to upgrade to
3.4.x ensemble just yet and so we run w/ a 3.4.x client against 3.3.x ensemble.
@Jesse Sounds fine requiring 3.4.x in 0.96. Want to raise a conversation out
on mailing list?
> ZKUtil deleteRecursively should be a recoverable operation
> ----------------------------------------------------------
>
> Key: HBASE-5790
> URL: https://issues.apache.org/jira/browse/HBASE-5790
> Project: HBase
> Issue Type: Improvement
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Labels: zookeeper
> Fix For: 0.96.0, 0.94.1
>
> Attachments: java_HBASE-5790-v1.patch, java_HBASE-5790.patch
>
>
> As of 3.4.3 Zookeeper now has full, multi-operation transaction. This means
> we can wholesale delete chunks of the zk tree and ensure that we don't have
> any pesky recursive delete issues where we delete the children of a node, but
> then a child joins before deletion of the parent. Even without transactions,
> this should be the behavior, but it is possible to make it much cleaner now
> that we have this new feature in zk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
