Getting Started with Your First Topology - Real-time Analytics with Storm and Cassandra - page 39

storm.local.dir: "/usr/local/storm/tmp"
◦ nimbus.host : The nodes need to know which machine is the master in
order to download topology jars and confs. This property is used for this
purpose:
nimbus.host: "<IP_ADDRESS_OF_NIMBUS_HOST>"
◦ java.library.path : This is the load path for the native libraries
that Storm uses (ZeroMQ and JZMQ). The default of /usr/local/
lib:/opt/local/lib:/usr/lib should be fine for most installa-
tions, so validate the libraries in the previously mentioned locations be-
fore moving forward.
◦ storm.messaging.netty : Storm's Netty-based transport has been
overhauled to significantly improve performance through better utiliza-
tion of thread, CPU, and network resources, particularly in cases where
message sizes are small. In order to provide Netty support, the following
configurations need to be added:
storm.messaging.transport:"backtype.storm.messaging.netty.Context"
storm.messaging.netty.server_worker_threads:1
storm.messaging.netty.client_worker_threads:1
storm.messaging.netty.buffer_size:5242880
storm.messaging.netty.max_retries:100
storm.messaging.netty.max_wait_ms:1000
storm.messaging.netty.min_wait_ms:100
◦ The storm.yaml snippet from our Storm cluster installation is as fol-
lows:
#To be filled in for a storm configuration
storm.zookeeper.servers:
- "nim-zkp-flm-3.abc.net"
storm.zookeeper.port: 2182
storm.local.dir: "/usr/local/storm/tmp"
nimbus.host: "nim-zkp-flm-3.abc.net"
topology.message.timeout.secs: 60