Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to configure strom.yaml, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

Configure storm.yaml

The storm distribution contains some configuration information in conf/storm.yaml. You can see the default configuration here. The configuration in storm.yaml is higher than that in default.xml. Here are the configurations necessary to run the storm cluster:

1. Storm.zookeeper.servers the address of the zookeeper cluster used to configure the storm cluster, such as:

Storm.zookeeper.servers:

-"111.222.333.444"

-"555.666.777.888"

2. Storm.local.dir Nimbus and Supervisor need a directory on the local disk to store some status information (jar packages, configuration files, etc.) you should create that directory on each machine and assign the correct permissions, such as:

Storm.local.dir: "/ mnt/storm"

3. Java.library.path this is the load address of the local dependencies (ZeroMQ and JZMQ) that storm depends on. The default is: / usr/local/lib:/opt/local/lib:/usr/lib, which is correct in most cases, so you should not have to change this configuration.

4. Nimbus.host all working machines need the address of the nimbus machine so that they know where to get the jar package and configuration files:

Nimbus.host: "111.222.333.44"

5. Supervisor.slots.ports for each worker machine, this configuration specifies how many worker processes are running on this worker machine, each process uses a separate port to receive messages, and this configuration also specifies which ports to use. If you define five ports here, storm will assign up to five worker processes on this machine. If three ports are assigned, then a maximum of three processes will be assigned. The default configuration is 4:

Supervisor.slots.ports:

-6700

-6701

-6702

-6703

Start the daemon

The final step is to start all daemons for storm. As mentioned earlier, there should be monitoring for each process! Storm is a fail-fast system that exits when any unpredictable error occurs. Storm is designed to exit safely at any time and restart correctly at any time, which is why storm does not store state online-if Nimbus and Supervisor are restarted, it will not affect the running topology. Here's how to start these threads:

Nimbus runs bin/storm nimbus on a Nimbus machine

Supervisor runs bin/storm supervisor on each work machine, and supervisor is responsible for starting and terminating work processes on the work machine.

UI storm UI is a website that can check the running status of storm, run through bin/storm ui, and visit http://{nimbus.host}:8080/.

As you can see, running a storm cluster is simple. These processes log into the subdirectory logs of the directory where you unzipped the storm distribution.

Thank you for reading this article carefully. I hope the article "how to configure strom.yaml" shared by the editor will be helpful to everyone. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.