Hi,
We're evaluating storm as our real time stream processing
infrastructure. We are a SaaS company, and the stream has messages from
different customers. Some of our customers may generate a large volume of
messages, starving messages from other customers. We've a custom throttling
logic built on top of Akka in another context, but was wondering if there
is a way of plugging in a custom throttling strategy in to Storm.
topology.max.spout.pending
does not server our purpose. Any pointers are appreciated
Thanks
-Neelesh