- Mastering Apache Storm
- Ankit Jain
- 183字
- 2021-07-02 20:32:32
Task
This is the most granular unit of task execution in Storm. Each task is an instance of a spout or bolt. When defining a Storm topology, you can specify the number of tasks for each spout and bolt. Once defined, the number of tasks cannot be changed for a component at runtime. Each task can be executed alone or with another task of the same type, or another instance of the same spout or bolt.
The following diagram depicts the relationship between a worker process, executors, and tasks. In the following diagram, there are two executors for each component, with each hosting a different number of tasks.
Also, as you can see, there are two executors and eight tasks defined for one component (each executor is hosting four tasks). If you are not getting enough performance out of this configuration, you can easily change the number of executors for the component to four or eight to increase performance and the tasks will be uniformly distributed between all executors of that component. The following diagrams show the relationship between executor, task, and worker:

- Mastering Entity Framework Core 2.0
- 深度實踐OpenStack:基于Python的OpenStack組件開發
- 造個小程序:與微信一起干件正經事兒
- PostgreSQL Cookbook
- Ext JS Data-driven Application Design
- Mastering Natural Language Processing with Python
- Visual Basic程序設計教程
- 64位匯編語言的編程藝術
- 用戶體驗增長:數字化·智能化·綠色化
- SQL 經典實例
- 超好玩的Scratch 3.5少兒編程
- DB2SQL性能調優秘笈
- Practical Maya Programming with Python
- Test-Driven iOS Development with Swift
- 高性能PHP 7