[
https://issues.apache.org/jira/browse/STORM-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376136#comment-14376136
]
Sriharsha Chintalapani commented on STORM-617:
----------------------------------------------
[~revans2] I think users need to pass in storm.zookeeper.topology.auth.payload
? . ZookeerpAuthInfo picks this first if its available than look for
storm.zookeeper.auth.payload if previous one is not available.
> In Storm secure mode re-deploying trident topology causes zookeeper ACL issue
> -----------------------------------------------------------------------------
>
> Key: STORM-617
> URL: https://issues.apache.org/jira/browse/STORM-617
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Sriharsha Chintalapani
> Assignee: Sriharsha Chintalapani
> Priority: Blocker
>
> This issue is caused by this line
> https://github.com/apache/storm/blob/master/storm-core/src/jvm/backtype/storm/transactional/state/TransactionalState.java#L67
> If the storm cluster nimbus is running with a kerberos principal named
> "nimbus"
> and supervisors are running with principal "storm" . Storm puts the acl on
> trident spout using principal "nimbus" and this won't be able to accessed or
> modified by supervisor since they are logging into zookeeper as user "storm".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
