rocketMq combat (4) - cluster configuration

For the installation and configuration of rocketmq, please refer to the following, and the attached e-book user guide 3.2.4 page 44 has related content

http://chenchangqun.iteye.com/admin/blogs/2341749

 

Here we talk about the configuration of multi-master and multi-asynchronous replication mode, assuming 2 masters, 2 slaves, 2 nameservers, and the environment has been configured,

The nameservers are all started.

Then the command is as follows

/opt/ali-rocketmq/devenv is the directory where rocketmq is installed. Note that multiple nameservers are separated by semicolons

master1 starts

nohup sh mqbroker -n "10.103.16.77:9876;10.103.16.15:9876" -c /opt/ali-rocketmq/devenv/conf/2m-2s-async/broker-a.properties &

slave1 starts

nohup sh mqbroker -n "10.103.16.77:9876;10.103.16.15:9876" -c /opt/ali-rocketmq/conf/2m-2s-async/broker-a-s.properties &

master2 starts

nohup sh mqbroker -n "10.103.16.77:9876;10.103.16.15:9876" -c /opt/ali-rocketmq/devenv/conf/2m-2s-async/broker-b.properties &

slave2 starts

nohup sh mqbroker -n "10.103.16.77:9876;10.103.16.15:9876" -c /opt/ali-rocketmq/conf/2m-2s-async/broker-b-s.properties &

After the current rocketmq version master hangs up, it cannot be produced and can continue to be consumed from the slave.

 

After executing the command, you can simulate the master or the slave to hang up to test it.