Database Reference
In-Depth Information
Configuring Storm
Storm keeps its base configuration in the
conf/storm.yaml
file. This does
not contain information about topologies, but it does keep track of a few
importantfeatures:thelocationoftheZooKeeperservers,thelocationofthe
nimbus server, and the transport mechanism.
It is assumed that a ZooKeeper cluster similar to the one configured in
Chapter 3 is currently running. Like all ZooKeeper clients, Storm needs
to know the name of at least one ZooKeeper server. More servers provide
failover in case that server is temporarily unavailable. The servers are
provided as a YAML list for the configuration parameter
storm.zookeeper.servers
:
storm.zookeeper.servers:
- "zookeeper-node1.mydomain.net"
- "zookeeper-node2.mydomain.net"
If you're running a distributed server on a single machine, just use
localhost
here:
storm.zookeeper.servers:
- "localhost"
To be able to submit topologies, Storm also needs to know the location of
the nimbus server:
nimbus.host: "storm-nimbus.mydomain.net"
If you're running everything locally, this should also be set to
localhost
:
nimbus.host: "localhost"
If you're using Storm 0.9.0, use the Netty transport instead of the ZeroMQ
transport. Contributed by Yahoo!, the Netty transport offers better
performance and easier setup and should be the default on all clusters.
However, it is not the default for Storm clusters, so you need to configure it
by adding the following statements to the configuration file:
storm.messaging.transport:
"backtype.storm.messaging.netty.Context"
