Hi there, we are using storm for our real-time processing system, and so far, so good!
We have some questions about when we add nodes (autoscaling on EC2), and when we terminate others (based on CPU, for example). Right now, we are seeing that if we add new nodes into the system, Storm just stops for around a 30 seconds (tuple timeout), rebalances itself and new nodes work as expected. Downtime of ~50 seconds But, if a node goes down, we see a drop in the processing (to 0 tuples) for around 3 minutes, after that we see that it slowly start to rise the processing speed, and after one minute, everything is OK (total of 4 minutes or so) Is there any way to not to wait 3 minutes, but the tuple timeout? (or something similar, like on added nodes) Thanks for your ideas
signature.asc
Description: Message signed with OpenPGP using GPGMail
