[
https://issues.apache.org/jira/browse/HBASE-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555314#comment-13555314
]
stack commented on HBASE-7382:
------------------------------
[~enis] IMO, we cannot require that an hbase deploy force a zk ensemble update.
3.4 client will go against 3.3. ensemble except when 3.4 tries to do a multi
([~gchanan] and crew wrote up in another issue about how we can't ask the
ensemble if it 3.4 and even then, we want to be guard against case where one
ensemble member is 3.4 but rest are 3.3 -- its ugly). Or, you think we should
add a prereq for 0.96? That the ensemble be 3.4? (Meantime I added to the
refguide a todo for explaining 3.4 and multi, etc.)
> Port ZK.multi support from HBASE-6775 to 0.96
> ---------------------------------------------
>
> Key: HBASE-7382
> URL: https://issues.apache.org/jira/browse/HBASE-7382
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
> Reporter: Gregory Chanan
> Fix For: 0.96.0
>
>
> HBASE-6775 adds support for ZK.multi ZKUtil and uses it for the 0.92/0.94
> compatibility fix implemented in HBASE-6710.
> ZK.multi support is most likely useful in 0.96, but since HBASE-6710 is not
> relevant for 0.96, perhaps we should find another use case first before we
> port.
--
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
