RocketMQ集群模型与搭建
1.各角色介绍
Producer:消息的发送者;
Consumer:消息的接收者;
Broker:暂存和传输消息;
NameServer:管理Broker;
Topic:区分消息的种类;一个发送者可以发送消息给一个或者多个Topic;一个消息的接收者可以订阅一个或多个Topic消息
Message Queue:相当于是Topic的分区;用于并行发送和接收消息
![在这里插入图片描述](https://i-blog.csdnimg.cn/blog_migrate/b35b2f49ea9da165aad8660be31ad5b9.png)
2. 集群搭建方式
集群特点
NameServer是一个几乎无状态节点,可集群部署,节点之间无任何信息同步
Broker不是相对复杂,Broker分为Master与Slave,一个Master可以对应多个Slave,但是一个Slave只能对应一个Master,Master与Slave的对应关系通过指定相同的BrokerName,不同的BrokerId来定义,BrokerID为0表示Master,非0表示Slave。Master也可以部署多个。每个Broker与NameServer集群中的所有节点建立长连接,定时注册Topic信息到所有NameServer。
Producer与NameServer集群中的其中一个节点(随机选择)建立长连接,定期从NameSer取Topic路由信息,并向提供Topic服务的Master建立长连接,且定时向Master发送心跳。Producer完全无状态,可集群部署
Consumer与NameServer集群中其中一个节点(随机选择)长连接,定期从NameServer取Topic路由信息,并向提供Topic服务的Master,Slave建立长连接,且定时向Master,Slave发送心跳。Consumer即可以从Master订阅消息,也可以从Slave订阅消息,订阅规则由Broker配置决定
3. 集群模式
3.1 单Master模式
这种方式风险较大,一旦Brocker重启或者宕机时,会导致整个服务不可用。不建议线上环境使用,可以用于本地测试
3.2 多Master模式
一个集群无Slave,全是Master
优点:配置简单,单个Master宕机或重启维护对应用无影响,在磁盘配置为RAID10时,即使集器宕机不可恢复情况下,由于RAID10磁盘非常可靠,消息也不会丢(异步刷盘丢失少量消息,同步刷盘一条不丢),性能最高
缺点:单台集器宕机期间,这台机器上未被消费的消息在集器恢复之前不可订阅,消息实时性会收到影响。
3.3 多Master多Slave模式(异步)
每个Master配置一个Slave,有多对Master-Slave,HA采用异步复制方式,主备有短暂消息延迟(毫秒级),这种模式的优缺点如下:
优点:即使磁盘损坏,消息丢失的非常少,且消息实时性不会受影响,同时Master宕机后,消费者仍然可以从Slave消费,而且此过程对应用透明,不需要人工干预,性能同多Master模式i几乎一样
缺点:Master宕机,磁盘损坏情况下会丢失少量消息。
3.4 多Master多Slave模式(同步)
每个Master配置一个Slave,有多对Master-Slave,HA采用同步双写方式,即只有主备都写成功,才向应用返回成功,这种模式的优缺点如下
优点:数据与服务都无单点故障,Master宕机情况下,消息无延迟,服务可用性与数据可用性都非常高
缺点:性能比异步复制模式略低(大约低10%左右),发送单个消息的RT会略高,且目前版本在主节点宕机后,备机不能自动切换为主机。
二. 集群环境搭建
![在这里插入图片描述](https://i-blog.csdnimg.cn/blog_migrate/09fba3619b61e5470e09c97ee47d0b44.png)
搭建
2m2s
集群
下面通过
docker
搭建
2master+2slave
的集群。
#
创建
2
个
master
#nameserver1
docker create
-p
9876
:9876
--name
rmqserver01 \
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-v
/haoke/rmq/rmqserver01/logs:/opt/logs \
-v
/haoke/rmq/rmqserver01/store:/opt/store \
foxiswho/rocketmq:server-4.3.2
#nameserver2
docker create
-p
9877
:9876
--name
rmqserver02 \
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-v
/haoke/rmq/rmqserver02/logs:/opt/logs \
-v
/haoke/rmq/rmqserver02/store:/opt/store \
foxiswho/rocketmq:server-4.3.2
#
创建第
1
个
master broker
#master broker01
docker create
--net
host
--name
rmqbroker01 \
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-v
/haoke/rmq/rmqbroker01/conf/broker.conf:/etc/rocketmq/broker.conf \
-v
/haoke/rmq/rmqbroker01/logs:/opt/logs \
-v
/haoke/rmq/rmqbroker01/store:/opt/store \
foxiswho/rocketmq:broker-4.3.2
#
配置
namesrvAddr
=
172
.16.55.185:9876;172.16.55.185:9877
brokerClusterName
=
ItcastCluster
brokerName
=
broker01
brokerId
=
0
deleteWhen
=
04
fileReservedTime
=
48
brokerRole
=
SYNC_MASTER
flushDiskType
=
ASYNC_FLUSH
brokerIP1
=
172
.16.55.185
brokerIp2
=
172
.16.55.185
listenPort
=
10911
namesrvAddr
=
172
.16.55.185:9876;172.16.55.185:9877
brokerClusterName
=
ItcastCluster
brokerName
=
broker01
brokerId
=
0
deleteWhen
=
04
fileReservedTime
=
48
brokerRole
=
SYNC_MASTER
flushDiskType
=
ASYNC_FLUSH
brokerIP1
=
172
.16.55.185
brokerIp2
=
172
.16.55.185
listenPort
=
10911
#
创建第
2
个
master broker
#master broker02
docker create
--net
host
--name
rmqbroker02 \
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-v
/haoke/rmq/rmqbroker02/conf/broker.conf:/etc/rocketmq/broker.conf \
-v
/haoke/rmq/rmqbroker02/logs:/opt/logs \
-v
/haoke/rmq/rmqbroker02/store:/opt/store \
foxiswho/rocketmq:broker-4.3.2
#master broker02
namesrvAddr
=
172
.16.55.185:9876;172.16.55.185:9877
brokerClusterName
=
ItcastCluster
brokerName
=
broker02
brokerId
=
0
deleteWhen
=
04
fileReservedTime
=
48
brokerRole
=
SYNC_MASTER
flushDiskType
=
ASYNC_FLUSH
brokerIP1
=
172
.16.55.185
brokerIp2
=
172
.16.55.185
listenPort
=
10811
#
创建第
1
个
slave broker
#slave broker01
docker create
--net
host
--name
rmqbroker03 \
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-v
/haoke/rmq/rmqbroker03/conf/broker.conf:/etc/rocketmq/broker.conf \
-v
/haoke/rmq/rmqbroker03/logs:/opt/logs \
-v
/haoke/rmq/rmqbroker03/store:/opt/store \
foxiswho/rocketmq:broker-4.3.2
#slave broker01
namesrvAddr
=
172
.16.55.185:9876;172.16.55.185:9877
brokerClusterName
=
ItcastCluster
brokerName
=
broker01
brokerId
=
1
deleteWhen
=
04
fileReservedTime
=
48
brokerRole
=
SLAVE
flushDiskType
=
ASYNC_FLUSH
brokerIP1
=
172
.16.55.185
brokerIp2
=
172
.16.55.185
listenPort
=
10711
#
创建第
2
个
slave broker
#slave broker01
docker create
--net
host
--name
rmqbroker04 \
-e
"JAVA_OPTS=-Duser.home=/opt"
\
-e
"JAVA_OPT_EXT=-server -Xms128m -Xmx128m -Xmn128m"
\
-v
/haoke/rmq/rmqbroker04/conf/broker.conf:/etc/rocketmq/broker.conf \
-v
/haoke/rmq/rmqbroker04/logs:/opt/logs \
-v
/haoke/rmq/rmqbroker04/store:/opt/store \
foxiswho/rocketmq:broker-4.3.2
#slave broker02
namesrvAddr
=
172
.16.55.185:9876;172.16.55.185:9877
brokerClusterName
=
ItcastCluster
brokerName
=
broker02
brokerId
=
1
deleteWhen
=
04
fileReservedTime
=
48
brokerRole
=
SLAVE
flushDiskType
=
ASYNC_FLUSH
brokerIP1
=
172
.16.55.185
brokerIp2
=
172
.16.55.185
listenPort
=
10611
#
启动容器
docker
start
rmqserver01 rmqserver02
docker
start
rmqbroker01 rmqbroker02 rmqbroker03 rmqbroker04