[
https://issues.apache.org/jira/browse/SLIDER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183810#comment-14183810
]
Sumit Mohanty commented on SLIDER-564:
--------------------------------------
As part of this JIRA, I am going to make the following changes:
* Irrespective of security state, create a default ZK node if application
package asks for it
* The default node will not be associated with any ACL and application is
responsible for adding ACLs to sub-nodes as needed (this is what HBase also
does when running in traditional fashion)
* Remove warning when delete fails
> handle --zkpath argument in a secure cluster
> --------------------------------------------
>
> Key: SLIDER-564
> URL: https://issues.apache.org/jira/browse/SLIDER-564
> Project: Slider
> Issue Type: Task
> Components: client
> Affects Versions: Slider 0.50
> Reporter: Steve Loughran
> Assignee: Sumit Mohanty
> Fix For: Slider 0.60
>
>
> SLIDER-134 added a default node for an application instance.
> Looking at the {{createZookeeperNode()}} class, it does nothing if the
> cluster is secure. Which means that any expectation that slider is going to
> set up a default path will be false in this situation.
> We need to decide the policy here and then implement it. As setting up secure
> ZK paths is very hard (more precisely, knowing what permissions to pass down
> is very hard), it is simplest to delegate to the user/ZK cluster admins. In
> which case the client should fail if a {{--zkpath}} attribute is passed in at
> build time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
