You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by churly lin <ch...@gmail.com> on 2013/12/31 09:23:42 UTC
Is there a way to prevent someone else killing my topology?
Hi, all:
Suppose that I have a running topology, How can I prevent sb else killing
my topology in production environment?
I consider that there are two aspect:
1. To prevent sb else killing my topology by command line.
Suppose I run a topology by user storm1, Could someone else kills my
toploogy by using command "storm kill" as user storm2?(user storm2 could
submit a topology to the same storm cluster too.)
If the answer is YES, Is there a way to prevent it?
2. To prevent sb else killing my topology by Storm UI.
Anyone who can visit the Storm UI is able to kill the running topology
which was submitted by someone else. Is there a way to prohibit other
people to kill topology unlimited? Like iptables?
Thanks.
Re: Is there a way to prevent someone else killing my topology?
Posted by ch...@gmail.com.
Hi all,
I just wonder have you ever met this issue before and how you settle it?
Sent from myMail for iOS
2013年12月31日 星期二 16:23 +0800 from churly lin <ch...@gmail.com>:
Hi, all:
Suppose that I have a running topology, How can I prevent sb else killing my topology in production environment?
I consider that there are two aspect:
1. To prevent sb else killing my topology by command line.
Suppose I run a topology by user storm1, Could someone else kills my toploogy by using command "storm kill" as user storm2?(user storm2 could submit a topology to the same storm cluster too.)
If the answer is YES, Is there a way to prevent it?
2. To prevent sb else killing my topology by Storm UI.
Anyone who can visit the Storm UI is able to kill the running topology which was submitted by someone else. Is there a way to prohibit other people to kill topology unlimited? Like iptables?
Thanks.