[
https://issues.apache.org/jira/browse/STORM-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376721#comment-14376721
]
ASF GitHub Bot commented on STORM-587:
--------------------------------------
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/475
STORM-587. trident transactional state in zk should be namespaced with
topology id.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-719
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/475.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #475
----
commit 8a264ad177595529991403fa6b2842d561e2b4b3
Author: Sriharsha Chintalapani <[email protected]>
Date: 2015-03-23T21:24:12Z
STORM-587. trident transactional state in zk should be namespaced with
topology id.
----
> 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
> Reporter: Parth Brahmbhatt
>
> 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)
