You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2017/08/29 23:47:00 UTC

[jira] [Assigned] (SLIDER-564) handle --zkpath argument in a secure cluster

     [ https://issues.apache.org/jira/browse/SLIDER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Mohanty reassigned SLIDER-564:
------------------------------------

    Assignee:     (was: Sumit Mohanty)

> 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
>             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.4.14#64029)