Storm production environment Deployment issues

Because deploying a cluster firewall in a formal production environment cannot be turned off, it is helpful to add rules to the ports used in Storm Iptables

is the 2.6 kernel to add:

Vi /etc/sysconfig/iptables-a input -m state --state new -m tcp -p  tcp --dport     6700     -j ACCEPT-A  input -m state --state new -m tcp -p tcp --dport      6701     -j accept-a input -m state -- state new -m tcp -p tcp --dport     6702      -j accept-a input -m state --state new -m tcp - p tcp --dport     6703     -j accept# A list of ports on supervisor.slots.portssupervisor that can run workers. Each worker occupies one port, and only one w#orker is run per port. This configuration allows you to adjust the number of workers running on each machine. (Adjust slots/per machine)-a input -m state --state new -m tcp -p tcp -- dport     6704     -j accept  #此为nimbus. Thrift.portnimbus The thrift Listener port is 6627 -a by default  INPUT -m state --state NEW -m tcp -p tcp --dport      6627     -j accept

Is the 3.1 kernel that executes it:

/sbin/iptables-i input-p TCP--dport 6627-j ACCEPT

The Storm.yaml configuration is as follows:

Storm.zookeeper.servers:

-"HADOOP02"

-"HADOOP03"

-"HADOOP04"

#

Nimbus.host: "Hadoop01"

ui.port:38080

storm.zookeeper.port:2181

Storm.local.dir: "/home/common/storm/storm-0.9.5/data/"

Supervisor.slots.ports:

-6700

-6701

-6702

-6703

-6704

Storm production environment Deployment issues