[ 
https://issues.apache.org/jira/browse/KNOX-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320475#comment-16320475
 ] 

Larry McCay commented on KNOX-1149:
-----------------------------------

Hi [~rkellogg] - I think this looks like an important fix.
Unfortunately, the fact that it "should also correct issues with other Kerberos 
protected services" means two things:

1. this will require extensive testing across all services in a secure cluster
2. this will potentially change behavior for many services from 0.14.0

#1 will push out the 1.0.0 release and delay work on 1.1.0 and #2 will risk 
destabilizing 1.0.0 in a way that is different from 0.14.0.

My inclination is to leave it in 1.1.0 and get 1.0.0 out as is.
We can then immediately begin work on 1.1.0 and try and managed scope to get 
such fixes in.

Thoughts?


> 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
>             Fix For: 1.1.0
>
>         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)

Reply via email to