[
https://issues.apache.org/jira/browse/STORM-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309281#comment-14309281
]
Sriharsha Chintalapani commented on STORM-617:
----------------------------------------------
[~dagit] yes thats what causing this issue. In general most of the users I've
seen like to keep the principals for StormServer and StormClient different .
Example StormServer running nimbus/_HOST and StormClient running as Storm/_HOST.
Adding StormServer as another ACL entry will work.
> 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
> Reporter: Sriharsha Chintalapani
> Assignee: Sriharsha Chintalapani
>
> 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)
