[
https://issues.apache.org/jira/browse/KNOX-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317581#comment-16317581
]
Larry McCay commented on KNOX-1149:
-----------------------------------
[~rkellogg] - we are descoping 1.0.0 to make sure it is as functionally similar
to 0.14.0 as possible. I am curious whether your Minor priority here is
accurate. It seems like it is pretty broken for secure clusters this way.
Is there a workaround that I am unaware of?
> HBase High Availability Fails with Kerberos Secured Cluster
> -----------------------------------------------------------
>
> Key: KNOX-1149
> URL: https://issues.apache.org/jira/browse/KNOX-1149
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.13.0, 0.14.0
> Reporter: Rick Kellogg
> Assignee: Rick Kellogg
> Priority: Minor
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1149.patch
>
>
> When HBase is run on a Kerberos secured cluster, the registration of the
> Region Servers is stored in ZooKeeper under a different path. The
> HBaseZookeeperURLManager class used to support high availability in Knox
> needs to be updated to look in both locations and then ping for availability.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)