RocketMQ高手之路系列之三：RocketMQ之路由中心

}

}, 1, 10, TimeUnit.MINUTES);

if (TlsSystemConfig.tlsMode != TlsMode.DISABLED) {

// Register a listener to reload SslContext

try {

fileWatchService = new FileWatchService(

new String[] {

TlsSystemConfig.tlsServerCertPath,

TlsSystemConfig.tlsServerKeyPath,

TlsSystemConfig.tlsServerTrustCertPath

},

new FileWatchService.Listener() {

boolean certChanged, keyChanged = false;

@Override

public void onChanged(String path) {

if (path.equals(TlsSystemConfig.tlsServerTrustCertPath)) {

log.info(“The trust certificate changed, reload the ssl context”);

reloadServerSslContext();

}

if (path.equals(TlsSystemConfig.tlsServerCertPath)) {

certChanged = true;

}

if (path.equals(TlsSystemConfig.tlsServerKeyPath)) {

keyChanged = true;

}

if (certChanged && keyChanged) {

log.info(“The certificate and private key changed, reload the ssl context”);

certChanged = keyChanged = false;

reloadServerSslContext();

}

}

private void reloadServerSslContext() {

((NettyRemotingServer) remotingServer).loadSslContext();

}

});

} catch (Exception e) {

log.warn(“FileWatchService created error, can’t load the certificate dynamically”);

}

}

return true;

}

二、路由信息

---

NameServer主要是为了生产者以及消费者提供Topic的路由信息。那么路由信息是存在哪里呢？在RouteInfoManager源码中，可以查看到如下信息：

private final HashMap<String/* topic */, List> topicQueueTable;

private final HashMap<String/* brokerName */, BrokerData> brokerAddrTable;

private final HashMap<String/* clusterName /, Set<String/ brokerName */>> clusterAddrTable;

private final HashMap<String/* brokerAddr */, BrokerLiveInfo> brokerLiveTable;

private final HashMap<String/* brokerAddr /, List/ Filter Server */> filterServerTable;

1、 topicQueueTable

Topic消息队列路由信息，存储所有Topic的属性信息，消息发送时会根据路由表进行负载均衡；

它是一个HashMap的数据结构，对应的key值为Topic的名称，value为List<QueueData>，QueueData信息如下所示：

public class QueueData implements Comparable {

//Broker名称

private String brokerName;

//读队列长度

private int readQueueNums;

//写队列长度

private int writeQueueNums;

//读写去权限

private int perm;

//Topic同步标志

private int topicSynFlag;

…

}

2、 brokerAddrTable

存储Broker的属性信息，包括Broker基础信息，包含brokerName、所属集群名称，主备Broker地址；

对应的key只为BrokerName，value为BrokerData。BrokerData的相关属性如下所示：

public class BrokerData implements Comparable {

private String cluster;

private String brokerName;

private HashMap<Long/* brokerId /, String/ broker address */> brokerAddrs;

…

}

相同名称的Broker可能有多台机器，也就是说它可能是个集群，一个Master以及多个Slave。所以在BrokerData中，存储了相关的属性，即Broker的名称、所属集群的信息，以及对应的机器的地址信息。

3、clusterAddrTable

Broker集群信息，存储集群重点 所有Broker的名称；

key为集群的名称，value为Broker名称的集合。

4、brokerLiveTable

Broker及其的实时状态信息，NameServer每次收到心跳探测包会进行状态信息更新；

key值为 Broker的地址，对应一台机器，value为BrokerLiveInfo，它保存着对应Broker服务器的地址信息。lastUpdateTimestamp表示上次的状态更新时间，NameServer定时检查这个时间出的实时性，如果发现这个时间戳超过一定时间没有进行更新，则会将该Broker的地址从列表中进行删除。

class BrokerLiveInfo {

//最后更新时间

private long lastUpdateTimestamp;

//数据版本号

private DataVersion dataVersion;

//连接信息

private Channel channel;

//服务器地址

private String haServerAddr;

…

}

5、filterServerTable

存储过滤服务器信息，Broker上的FilterServer列表，用于类模式消息过滤。对应的key值为Broker地址，value为FilterServer的地址列表。

三、路由注册

---

在第二小节中，我们介绍了路由信息的相关内容。那么在RocketMQ体系中，路由注册时如何实现的呢？路由注册通过Broker与NameServer之间心跳连接进行的。当Broker服务启动之后，就会向集群中的所有的NameServer发送心跳探测包。正常运行之后，Broker会每隔三十秒向集群中的所有NameServer发送心跳检测包。当接收到心跳检测包时，NameServer会更新brokerLiveTable缓存中的BrokerLiveInfo的lastUpdateTimestamp时间戳。与此同时，NameServer会每隔10s对brokerLiveTable进行扫描，如果发现连续120s未检测到心跳，则会将该Broker路由信息进行移除，流程如下所示：

在BrokerController中，通过调用它的start()方法，进行Broker端的心跳包发送，逻辑代码如下所示：

this.scheduledExecutorService.scheduleAtFixedRate(new Runnable() {

@Override

public void run() {

try {

//注册所有Broker

BrokerController.this.registerBrokerAll(true, false, brokerConfig.isForceRegister());

} catch (Throwable e) {

log.error(“registerBrokerAll Exception”, e);

}

}

}, 1000 * 10, Math.max(10000, Math.min(brokerConfig.getRegisterNameServerPeriod(), 60000)), TimeUnit.MILLISECONDS);

在registerBrokerAll方法中调用了doRegisterBrokerAll方法，如下所示：

private void doRegisterBrokerAll(boolean checkOrderConfig, boolean oneway,

TopicConfigSerializeWrapper topicConfigWrapper) {

List registerBrokerResultList = this.brokerOuterAPI.registerBrokerAll(

this.brokerConfig.getBrokerClusterName(),

this.getBrokerAddr(),

this.brokerConfig.getBrokerName(),

this.brokerConfig.getBrokerId(),

this.getHAServerAddr(),

topicConfigWrapper,

this.filterServerManager.buildNewFilterServerList(),

oneway,

this.brokerConfig.getRegisterBrokerTimeoutMills(),

this.brokerConfig.isCompressedRegister());

if (registerBrokerResultList.size() > 0) {

RegisterBrokerResult registerBrokerResult = registerBrokerResultList.get(0);

if (registerBrokerResult != null) {

if (this.updateMasterHAServerAddrPeriodically && registerBrokerResult.getHaServerAddr() != null) {

this.messageStore.updateHaMasterAddress(registerBrokerResult.getHaServerAddr());

}

this.slaveSynchronize.setMasterAddr(registerBrokerResult.getMasterAddr());

if (checkOrderConfig) {

this.getTopicConfigManager().updateOrderTopicConfig(registerBrokerResult.getKvTable());

}

}

}

}

在BrokerOuterAPI中调用registerBrokerAll方法获取所有注册的Broker列表：

public List registerBrokerAll(

//集群名称

final String clusterName,

//broker地址

final String brokerAddr,

//broker名称

final String brokerName,

//broker ID

final long brokerId,

//master地址

final String haServerAddr,

final TopicConfigSerializeWrapper topicConfigWrapper,

final List filterServerList,

final boolean oneway,

final int timeoutMills,

final boolean compressed) {

final List registerBrokerResultList = Lists.newArrayList();

List nameServerAddressList = this.remotingClient.getNameServerAddressList();

if (nameServerAddressList != null && nameServerAddressList.size() > 0) {

final RegisterBrokerRequestHeader requestHeader = new RegisterBrokerRequestHeader();

requestHeader.setBrokerAddr(brokerAddr);

requestHeader.setBrokerId(brokerId);

requestHeader.setBrokerName(brokerName);

requestHeader.setClusterName(clusterName);

requestHeader.setHaServerAddr(haServerAddr);

requestHeader.setCompressed(compressed);

RegisterBrokerBody requestBody = new RegisterBrokerBody();

requestBody.setTopicConfigSerializeWrapper(topicConfigWrapper);

requestBody.setFilterServerList(filterServerList);

final byte[] body = requestBody.encode(compressed);

final int bodyCrc32 = UtilAll.crc32(body);

requestHeader.setBodyCrc32(bodyCrc32);

final CountDownLatch countDownLatch = new CountDownLatch(nameServerAddressList.size());

//遍历所有NameServer列表

for (final String namesrvAddr : nameServerAddressList) {

brokerOuterExecutor.execute(new Runnable() {

@Override

public void run() {

try {

//分别向NameServer进行注册

RegisterBrokerResult result = registerBroker(namesrvAddr,oneway, timeoutMills,requestHeader,body);

if (result != null) {

registerBrokerResultList.add(result);

}

log.info(“register broker to name server {} OK”, namesrvAddr);

} catch (Exception e) {

log.warn(“registerBroker Exception, {}”, namesrvAddr, e);

} finally {

countDownLatch.countDown();

}

}

});

}

try {

countDownLatch.await(timeoutMills, TimeUnit.MILLISECONDS);

} catch (InterruptedException e) {

}

}

return registerBrokerResultList;

}

四、路由删除

---

NameServer每隔10s会对brokerLiveTable状态表进行扫描，扫描时如果发现BrokerLive中的lastUpdateTimestamp的时间戳信息与当前时间相差超过120s，则认为此时的Broker已经失活了，需要将其进行移除操作，同时还需要关闭对应的连接。接下来我们看下具体的代码：

在进行NamesrvCntroller示例初始化时，会进行定时检测任务。

this.scheduledExecutorService.scheduleAtFixedRate(new Runnable() {

@Override

public void run() {

NamesrvController.this.routeInfoManager.scanNotActiveBroker();

}

}, 5, 10, TimeUnit.SECONDS);

在RouteInfoManager中的scanNotActiveBroker()方法，主要用于遍历brokerLiveInfo路由表信息，通过检测BrokerLiveInfo中的lastUpdateTimestamp字段，该时间戳信息为上次收到心跳检测包的时间，判断该时间信息与当前的时间之差是否超过了120s。

public void scanNotActiveBroker() {

//获取在线Broker列表

Iterator<Entry<String, BrokerLiveInfo>> it = this.brokerLiveTable.entrySet().iterator();

while (it.hasNext()) {

Entry<String, BrokerLiveInfo> next = it.next();

//获取对应的接收到心跳包的更新时间

long last = next.getValue().getLastUpdateTimestamp();

if ((last + BROKER_CHANNEL_EXPIRED_TIME) < System.currentTimeMillis()) {

RemotingUtil.closeChannel(next.getValue().getChannel());

it.remove();

log.warn(“The broker channel expired, {} {}ms”, next.getKey(), BROKER_CHANNEL_EXPIRED_TIME);

this.onChannelDestroy(next.getKey(), next.getValue().getChannel());

}

}

}

在onChannelDestroy方法中进行路由表的相关删除操作，如下所示：

public void onChannelDestroy(String remoteAddr, Channel channel) {

String brokerAddrFound = null;

if (channel != null) {

try {

try {

this.lock.readLock().lockInterruptibly();

Iterator<Entry<String, BrokerLiveInfo>> itBrokerLiveTable =

this.brokerLiveTable.entrySet().iterator();

while (itBrokerLiveTable.hasNext()) {

Entry<String, BrokerLiveInfo> entry = itBrokerLiveTable.next();

if (entry.getValue().getChannel() == channel) {

brokerAddrFound = entry.getKey();

break;

}

}

} finally {

this.lock.readLock().unlock();

}

} catch (Exception e) {

log.error(“onChannelDestroy Exception”, e);

}

}

if (null == brokerAddrFound) {

brokerAddrFound = remoteAddr;

} else {

log.info(“the broker’s channel destroyed, {}, clean it’s data structure at once”, brokerAddrFound);

}

if (brokerAddrFound != null && brokerAddrFound.length() > 0) {

try {

try {

//申请写锁

this.lock.writeLock().lockInterruptibly();

//移除信息

this.brokerLiveTable.remove(brokerAddrFound);

this.filterServerTable.remove(brokerAddrFound);

String brokerNameFound = null;

boolean removeBrokerName = false;

Iterator<Entry<String, BrokerData>> itBrokerAddrTable =

this.brokerAddrTable.entrySet().iterator();

while (itBrokerAddrTable.hasNext() && (null == brokerNameFound)) {

BrokerData brokerData = itBrokerAddrTable.next().getValue();

Iterator<Entry<Long, String>> it = brokerData.getBrokerAddrs().entrySet().iterator();

while (it.hasNext()) {

Entry<Long, String> entry = it.next();

Long brokerId = entry.getKey();

String brokerAddr = entry.getValue();

if (brokerAddr.equals(brokerAddrFound)) {

brokerNameFound = brokerData.getBrokerName();

it.remove();

log.info(“remove brokerAddr[{}, {}] from brokerAddrTable, because channel destroyed”,

brokerId, brokerAddr);

break;

}

}

if (brokerData.getBrokerAddrs().isEmpty()) {

removeBrokerName = true;

itBrokerAddrTable.remove();

log.info(“remove brokerName[{}] from brokerAddrTable, because channel destroyed”,

brokerData.getBrokerName());

}

}

//对brokerAddrTable进行维护

if (brokerNameFound != null && removeBrokerName) {

Iterator<Entry<String, Set>> it = this.clusterAddrTable.entrySet().iterator();

while (it.hasNext()) {

Entry<String, Set> entry = it.next();

String clusterName = entry.getKey();

Set brokerNames = entry.getValue();

//移除brokerName

boolean removed = brokerNames.remove(brokerNameFound);

if (removed) {

log.info(“remove brokerName[{}], clusterName[{}] from clusterAddrTable, because channel destroyed”,

brokerNameFound, clusterName);

if (brokerNames.isEmpty()) {

log.info(“remove the clusterName[{}] from clusterAddrTable, because channel destroyed and no broker in this cluster”,

clusterName);

it.remove();

}

break;

}

}

}

//从clusterAddrTable中找到Broker从集群中进行删除

if (removeBrokerName) {

Iterator<Entry<String, List>> itTopicQueueTable =

this.topicQueueTable.entrySet().iterator();

while (itTopicQueueTable.hasNext()) {

Entry<String, List> entry = itTopicQueueTable.next();

String topic = entry.getKey();

List queueDataList = entry.getValue();

Iterator itQueueData = queueDataList.iterator();

while (itQueueData.hasNext()) {

QueueData queueData = itQueueData.next();

if (queueData.getBrokerName().equals(brokerNameFound)) {

//移除Topic信息

itQueueData.remove();

log.info(“remove topic[{} {}], from topicQueueTable, because channel destroyed”,

topic, queueData);

最后

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数Java工程师，想要提升技能，往往是自己摸索成长，自己不成体系的自学效果低效漫长且无助。

因此收集整理了一份《2024年Java开发全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Java开发知识点，不论你是刚入门Android开发的新手，还是希望在技术上不断提升的资深开发者，这些资料都将为你打开新的学习之门！

如果你觉得这些内容对你有帮助，需要这份全套学习资料的朋友可以戳我获取！！

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且会持续更新！

if (queueData.getBrokerName().equals(brokerNameFound)) {

//移除Topic信息

itQueueData.remove();

log.info(“remove topic[{} {}], from topicQueueTable, because channel destroyed”,

topic, queueData);

最后

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数Java工程师，想要提升技能，往往是自己摸索成长，自己不成体系的自学效果低效漫长且无助。

因此收集整理了一份《2024年Java开发全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

[外链图片转存中…(img-ou4sR98h-1714951488314)]

[外链图片转存中…(img-RCouFwqN-1714951488315)]

[外链图片转存中…(img-QBApqDkf-1714951488315)]

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Java开发知识点，不论你是刚入门Android开发的新手，还是希望在技术上不断提升的资深开发者，这些资料都将为你打开新的学习之门！

如果你觉得这些内容对你有帮助，需要这份全套学习资料的朋友可以戳我获取！！

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且会持续更新！