You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.
longdafeng edited this page Oct 13, 2014
·
2 revisions
Architecture
From a design perspective, Jstorm is a typical scheduling system
In this system,
Nimbus as a central scheduler is responsible for code distribution、task assignment
Supervisor as a deamon on each machine is responsible for workers' start and stop
Worker is the container of tasks
Task is the real executor of business logic
Zookeeper is the coordinator of the whole system
Work flow
Client submit one topology to nimbus
Nimbus assign task to different worker, generally the workers will be equal distributed in Supervisors. The task assignment will be stored in Zookeeper
Supervisor watch the Zookeeper, get to know which worker should be started and who will be shutdown.
If one worker has been started, it will fetch task assignment from Zookeeper and start the task's job.