Docker installation of RocketMQ and solutions to problems encountered during installation

This article mainly introduces the installation of rocketMQ4.4.0, which is mainly divided into four steps:
1. Pull the rocketmq image.
2. Create namesrv.
3. Create a broker node. What I am introducing here is how to create a single broker.
4. rocketMQ-console service, used to manage the management interface of rocketMQ.

Pull the rocketmq image

The docker command is as follows

docker pull rocketmqinc/rocketmq:4.4.0

Create namesrv

Docker Commands

docker run -d --name rmqnamesrv -p 9876:9876 -v C:\data\rocketmq\logs:/root/logs -v C:\data\rocketmq\store:/root/store -e "MAX_POSSIBLE_HEAP=100000000" rocketmqinc/rocketmq:4.4.0 sh mqnamesrv

Parameter Explanation

Create a single broker node

Docker Commands

docker run -d --name rmqbroker --link rmqnamesrv:namesrv -p 10911:10911 -p 10909:10909 --privileged=true -v C:\data\broker\logs:/root/logs -v C:\data\broker\store:/root/store -v C:\data\broker\conf\broker.conf:/opt/rocketmq-4.4.0/conf/broker.conf -e "NAMESRV_ADDR=namesrv:9876" -e "MAX_POSSIBLE_HEAP=200000000" rocketmqinc/rocketmq:4.4.0 sh mqbroker -c /opt/rocketmq-4.4.0/conf/broker.conf

Parameter Explanation

broker.conf file configuration

#If there are many nodes, you can configure multiple brokerClusterName = DefaultCluster
#broker name, master and slave use the same name, indicating their master-slave relationship brokerName = broker-a
#0 means Master, and values ​​greater than 0 mean different slaves
brokerId = 0
#Indicates the time to delete the message. The default is 4:00 a.m. deleteWhen = 04
#The length of time to keep messages on disk, in hours fileReservedTime = 48
#There are three values: SYNC_MASTER, ASYNC_MASTER, SLAVE; SYNC and ASYNC represent the mechanism for synchronizing data between Master and Slave;
brokerRole = ASYNC_MASTER
#Flushing strategy, the value is: ASYNC_FLUSH, SYNC_FLUSH means synchronous flushing and asynchronous flushing; SYNC_FLUSH message returns a success status only after it is written to the disk, ASYNC_FLUSH is not needed;
flushDiskType = ASYNC_FLUSH
# Set the IP address of the server where the broker node is located namesrvAddr = local IP address: 9876
brokerIP1 = local ip address

If the namesrvAddr configuration is not added to the broker.conf configuration file, the following error will be reported when the program is run:

Exception in thread "main" org.apache.rocketmq.remoting.exception.RemotingTooMuchRequestException: sendDefaultImpl call timeout
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendDefaultImpl(DefaultMQProducerImpl.java:588)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1223)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1173)
at org.apache.rocketmq.client.producer.DefaultMQProducer.send(DefaultMQProducer.java:214)
at com.baojian.mob.base.producer.SyncProducer.main(SyncProducer.java:41)
15:22:31.455 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true
15:22:32.049 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true

rocketMQ-console service

Docker Commands

You can directly execute the docker run command instead of using the docker pull command to pull the image. If the image does not exist, the image will be pulled first and then docker run will be executed.

docker run -d --name rmqadmin -e "JAVA_OPTS=-Drocketmq.namesrv.addr=172.16.122.115:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false" -p 8081:8080 pangliang/rocketmq-console-ng

Parameter Description

After the rocketmq-console interface container runs successfully, use a browser to open http://127.0.0.1:8081 to enter the rokcetmq-console management interface and see the cluster information, indicating that rocketmq has been installed successfully.

Rocketmq-console producer interface error

Click Search and an error message appears because the producer uses producer.shutdown() to close the production group after creating it. You can log out with the following code.

This is the end of this article about installing rocketMQ in docker and solving problems during the installation process. For more information about installing rocketMQ in docker, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future!