[
https://issues.apache.org/jira/browse/SLIDER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183816#comment-14183816
]
ASF subversion and git services commented on SLIDER-564:
--------------------------------------------------------
Commit 39a524455ea1b777f004e0efa826ef2c1521287a in incubator-slider's branch
refs/heads/develop from [~sumitmohanty]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=39a5244 ]
SLIDER-564. Ensure default ZK node is always created and do not warn during
delete if it does not exist
> 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 2.0.0
>
>
> 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)
