You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/03/24 01:51:53 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=14376901#comment-14376901 ]
Jungtaek Lim edited comment on STORM-587 at 3/24/15 12:51 AM:
--------------------------------------------------------------
I'm just curious about author's intention to make this constraint though it's easily avoided.
For example, if "stream" is reusable for whole cluster (just need to avoid to use concurrently) by concept.
In other words, topology has a own stream and it should be never changed, your patch works perfectly. If stream is independent to topology by concept, it may be better to confirm that we should kept the concept or discard it.
Maybe it was documented, so please correct me if I'm wrong.
was (Author: kabhwan):
I'm just curious about author's intention to make this constraint though it's easily avoided.
For example, if "stream" is reusable for whole cluster (just need to avoid to use concurrently) by concept.
In other words, topology has a own stream and it should be never changed, your patch works perfectly. If stream is independent to topology by concept, it may be better to confirm concept should be kept.
Maybe it was documented, so please correct me if I'm wrong.
> 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
> 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)