Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why is this not a trending topic? #4

Open
ppjogani opened this issue Mar 19, 2015 · 1 comment
Open

why is this not a trending topic? #4

ppjogani opened this issue Mar 19, 2015 · 1 comment

Comments

@ppjogani
Copy link

I am planing on using this capability to dynamically change spout objects. This seems to be pretty strong! Is this production quality?

@ptgoetz
Copy link
Owner

ptgoetz commented Mar 19, 2015

The answer is "yes", but it also depends...

storm-signals uses ZooKeeper, as does Storm. If you overload ZooKeeper, you will experience problems.

You should keep the byte[] payload smaller than the ZooKeeper size limit, and not overload it with too many signals.

Ultimately, the answer lies in your use case. If you're sending signals occasionally (e.g. a cron job), you'll be fine. If you're trying to send them at a high rate (many per second), you could run into trouble. What constitutes a "high rate" really depends on the fortitude of your ZooKeeper cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants