You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yufeng Jiang (JIRA)" <ji...@apache.org> on 2016/05/02 23:37:12 UTC
[jira] [Updated] (HBASE-15751) Fixed HBase compilation failure with
Zookeeper 3.5 and bumped HBase to use zookeeper 3.5
[ https://issues.apache.org/jira/browse/HBASE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yufeng Jiang updated HBASE-15751:
---------------------------------
Summary: Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use zookeeper 3.5 (was: Fixed HBase compilation failed with Zookeeper 3.5 and bump HBase to use zookeeper 3.5)
> Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use zookeeper 3.5
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-15751
> URL: https://issues.apache.org/jira/browse/HBASE-15751
> Project: HBase
> Issue Type: Task
> Components: Zookeeper
> Affects Versions: master
> Reporter: Yufeng Jiang
> Fix For: master
>
> Attachments: HBASE-15751.patch
>
>
> From zookeeper 3.5 and onwards, runFromConfig(QuorumPeerConfig config) method throws AdminServerException.
> HBase uses runFromConfig in HQuorumPeer.java and hence needs to throw this exception as well.
> I've created a patch to make HBase compatible with zookeeper-3.5.1-alpha. However, since zookeeper 3.5+ does not have a stable version yet, I don't think we should commit this patch. Instead, I suggest using this JIRA to track this issue. Once zookeeper releases stable version of 3.5+, I could create another patch to bump the zookeeper version in HBase trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)