You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 03:50:27 UTC

[jira] [Updated] (STORM-587) trident transactional state in zk should be namespaced with topology id

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

Rick Kellogg updated STORM-587:
-------------------------------
    Component/s: storm-core

> trident transactional state in zk should be namespaced with topology id
> -----------------------------------------------------------------------
>
>                 Key: STORM-587
>                 URL: https://issues.apache.org/jira/browse/STORM-587
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: Parth Brahmbhatt
>            Assignee: Sriharsha Chintalapani
>
> Currently when a trident transaction spout is initialized it creates a node in zk under /transactional with the spout name as the node's name. This is pretty dangerous as any other topology can be submitted with same spout name and  now these 2 spouts will be overwriting each other's states. I believe it is better to namespace this with topologyId just like all other zk entries under /storm.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)