[
https://issues.apache.org/jira/browse/HBASE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry He updated HBASE-16598:
-----------------------------
Hadoop Flags: Incompatible change
Release Note:
Deprecate the configuration property 'hbase.zookeeper.useMulti'.
useMulti will always be enabled. ZooKeeper 3.4.x and newer is required.
Internal:
The ZKUtil#multiOrSequential(ZooKeeperWatcher zkw, List<ZKUtilOp> ops, boolean
runSequentialOnMultiFailure) will not check 'hbase.zookeeper.useMulti' anymore,
and will always use multi.
It can still fall back to sequential operations if:
RunSequentialOnMultiFailure is true
On calling multi, we get a ZooKeeper exception that can be handled by a
sequential call.
> Enable zookeeper useMulti always and clean up in HBase code
> -----------------------------------------------------------
>
> Key: HBASE-16598
> URL: https://issues.apache.org/jira/browse/HBASE-16598
> Project: HBase
> Issue Type: Improvement
> Reporter: Jerry He
> Assignee: Jerry He
> Fix For: 2.0.0
>
> Attachments: HBASE-16598-v2.patch, HBASE-16598-v3.patch,
> HBASE-16598-v4.patch, HBASE-16598.patch
>
>
> We have zookeeper useMulti default true since HBase 1.0.0
> And in our Doc, "ZooKeeper 3.4.x is required as of HBase 1.0.0"
> The benefit of useMulti is obvious.
> Let's clean up the code to remove useMulti false case so that we don't have
> to continue with the hassle of maintaining two version of the code (e.g. in
> replication) . No go back to pre 3.4.x Zookeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
