官术网_书友最值得收藏!

Delving into the internals of Storm

Now that we know which physical components are present in a Storm cluster, let's understand what happens inside various Storm components when a topology is submitted. When we say topology submission, it means that we have submitted a distributed job to Storm Nimbus for execution over the cluster of supervisors. In this section, we will explain the various steps that are executed in various Storm components when a Storm topology is executed:

  • Topology is submitted on the Nimbus node.
  • Nimbus uploads the code jars on all the supervisors and instructs the supervisors to launch workers as per the NumWorker configuration or the TOPOLOGY_WORKERS configuration defined in Storm.
  • During the same duration all the Storm nodes (Nimbus and Supervisors) constantly co-ordinate with the Zookeeper clusters to maintain a log of workers and their activities.

As per the following figure, we have depicted the topology and distribution of the topology components, which are the same across clusters:

Delving into the internals of Storm

In our case, let's assume that our cluster constitutes of one Nimbus node, three Zookeepers in a Zookeeper cluster, and one supervisor node.

By default, we have four slots allocated to each supervisor, so four workers would be launched per Storm supervisor node unless the configuration is tweaked.

Let's assume that the depicted topology is allocated four workers, and it has two bolts each with a parallelism of two and one spout with a parallelism of four. So in total, we have eight tasks to be distributed across four workers.

So this is how the topology would be executed: two workers on each supervisor and two executors within each worker, as shown in the following figure:

Delving into the internals of Storm
主站蜘蛛池模板: 辽宁省| 渝北区| 根河市| 石景山区| 大姚县| 塔河县| 南江县| 寻乌县| 涿州市| 衡阳市| 宝坻区| 育儿| 泰和县| 河北区| 建德市| 揭阳市| 盐池县| 马公市| 廊坊市| 闵行区| 星子县| 来凤县| 麻城市| 汝阳县| 巩义市| 金溪县| 怀安县| 克拉玛依市| 永修县| 梓潼县| 叶城县| 方城县| 五常市| 法库县| 宜兰市| 丽江市| 松潘县| 上栗县| 华蓥市| 台东市| 保靖县|