Just want to clarify: The number of task is not the number parallel running bolt instances (called executors, which are threads). So I don't understand why you don't want to start with the maximum number of tasks? There should be almost no overhead if you have more tasks than executors (executors can process multiple tasks and switching between tasks is light weight). Adjusting the number of executors during runtime can be done without redeploying (-> "rebalance"), giving you the flexibility you need.
-Matthias On 06/19/2015 10:09 AM, Nilesh Chhapru wrote: > Hi Harshit, > > > > No there isn’t any way you can achieve this without redeploying your > topology, you may get this feature in the upcoming releases of storm as > this is in their roadmap. > > > > > > *Regards*, > > *Nilesh Chhapru.* > > > > *From:*Harshit Gupta [mailto:[email protected]] > *Sent:* 19 June 2015 11:43 AM > *To:* [email protected] > *Subject:* Fwd: DYNAMIC ADJUSTMENT OF NUMBER OF TASKS > > > > Hello, > > I am working on extending the Storm platform and would like to know the > scope of dynamically adjusting the number of tasks for a topology. > > I don't want to work with a worst-case ceiling on the number of tasks. > > Please let me know if there is/isn't a method for dynamically changing > the number of tasks without restarting the topology. > > Thanks. > > -- > > /With regards,/ > > * * > > *HARSHIT GUPTA* > > Fourth Year Undergraduate Student, > > Department Of Computer Science And Engineering, > > Indian Institute Of Technology, Kharagpur. >
signature.asc
Description: OpenPGP digital signature
