Hi Phil, I believe you can call Nimbus via it's Thrift interface and call the "Deactivate" and "Activate" functions, which pause and resume the topology spouts, respectively.
But in your case, I believe a better architecture would be to store the data into an intermediate queue, like Kafka. That way, you could scale your topology (Storm cluster) as needed to support the required throughput. Best regards, Danijel On Fri, Feb 21, 2014 at 4:33 AM, Phil Burress <[email protected]>wrote: > Is there a way to suspend a spout for a pre-determined period of time from > within that spout or an attached bolt? > As an example, assume that in your Topology you have a bolt retrieving > data from Twitter's api, but you get rate limited. To me the obvious > solution is to somehow suspend the spout for a period of time and then > resume processing. Is that possible? > > If that cannot be accomplished with the current architecture, are there > any other facilities in storm to handle a problem like this? > > Thanks very much! > -- Danijel Schiavuzzi
