说明：此代码是跟着《RocketMQ技术内幕》这本书阅读的，借鉴了很多东西，在此感谢丁威大佬和RocketMQ的贡献者们，文章如有问题，欢迎批评指正
RocketMQ版本：4.8.0
2、RocketMQ的注册中心NameServer
2.1 架构设计
- Producer、Consumer和NameServer各自集群之间是无状态的
- NameServer是专门为RocketMQ设计的注册中心，比zookeeper设计实现更加简单，在消息发送端提供容错机制来实现高可用
问题：为什么RocketMQ不使用Zookeeper作为注册中心呢？
答：
-
根据CAP理论，同时最多只能满足两个点，而zookeeper满足的是CP，也就是说zookeeper并不能保证服务的可用性，zookeeper在进行选举的时候，整个选举的时间太长，期间整个集群都处于不可用的状态，而这对于一个注册中心来说肯定是不能接受的，作为服务发现来说就应该是为可用性而设计。
-
基于性能的考虑，NameServer本身的实现非常轻量，而且可以通过增加机器的方式水平扩展，增加集群的抗压能力，而zookeeper的写是不可扩展的，而zookeeper要解决这个问题只能通过划分领域，划分多个zookeeper集群来解决，首先操作起来太复杂，其次这样还是又违反了CAP中的A的设计，导致服务之间是不连通的。
-
持久化的机制来带的问题，ZooKeeper 的 ZAB 协议对每一个写请求，会在每个 ZooKeeper 节点上保持写一个事务日志，同时再加上定期的将内存数据镜像（Snapshot）到磁盘来保证数据的一致性和持久性，而对于一个简单的服务发现的场景来说，这其实没有太大的必要，这个实现方案太重了。而且本身存储的数据应该是高度定制化的。
-
消息发送应该弱依赖注册中心，而RocketMQ的设计理念也正是基于此，生产者在第一次发送消息的时候从NameServer获取到Broker地址后缓存到本地，如果NameServer整个集群不可用，短时间内对于生产者和消费者并不会产生太大影响。
2.2 NameServer启动流程
启动位置：
NamesrvStartup.main()
- 解析开机命令，加载配置文件、端口等信息，填充namesrvConfig和nettyServerConfig属性
- 初始化NamesrvController
- 注册两个定时任务
NamesrvController.this.routeInfoManager.scanNotActiveBroker();
用于检测未激活的Broker，延迟5秒钟开始，每次检测间隔不超过10秒钟NamesrvController.this.kvConfigManager.printAllPeriodically();
用于打印KV配置，10秒一次
- 注册一个监听器，用于重新加载SslContext
// 编程小技巧：使用到了线程池等需要释放资源的时候，一种优雅的停机方式就是注册一个钩子函数，在jvm关闭之前释放资源
Runtime.getRuntime().addShutdownHook(new ShutdownHookThread(log, new Callable<Void>() {
@Override
public Void call() throws Exception {
controller.shutdown();
return null;
}
}));
2.3 NameServer的路由注册、故障剔除
2.3.1 路由元信息
代码位置：
RouteInfoManager.java
RouteInfopManager存储的信息如下
private static final InternalLogger log = InternalLoggerFactory.getLogger(LoggerName.NAMESRV_LOGGER_NAME);
private final static long BROKER_CHANNEL_EXPIRED_TIME = 1000 * 60 * 2;
private final ReadWriteLock lock = new ReentrantReadWriteLock();
// Topic消息队列的路由信息，消息发送时根据路由表进行负载均衡
private final HashMap<String/* topic */, List<QueueData>> topicQueueTable;
// Broker的基本信息，包括集群名称，Broker名称，主备地址等信息
private final HashMap<String/* brokerName */, BrokerData> brokerAddrTable;
// 集群信息，存储所有的Broker的名称
private final HashMap<String/* clusterName */, Set<String/* brokerName */>> clusterAddrTable;
// Broker的状态信息， NameServer每次接收心跳都会更新这里的信息，包括上次更新时间，数据版本等
private final HashMap<String/* brokerAddr */, BrokerLiveInfo> brokerLiveTable;
// Broker上的Filter Server列表，用于类模式过滤
private final HashMap<String/* brokerAddr */, List<String>/* Filter Server */> filterServerTable;
public class QueueData implements Comparable<QueueData> {
private String brokerName; // Broker名称
private int readQueueNums; // 读队列的个数
private int writeQueueNums; // 写队列的个数
private int perm;
private int topicSynFlag;
}
public class BrokerData implements Comparable<BrokerData> {
private String cluster; // 集群名称
private String brokerName; // Broker名称
private HashMap<Long/* brokerId */, String/* broker address */> brokerAddrs; // Broker对应其地址
private final Random random = new Random();
}
class BrokerLiveInfo {
// 上次心跳时间，距离现在超过120秒，NameServer会移除此Broker的路由信息同时关闭Socket连接
private long lastUpdateTimestamp;
private DataVersion dataVersion;
private Channel channel;
private String haServerAddr;
}
2.3.2 路由注册
路由注册是通过Broker和NameServer的心跳功能实现的，具体步骤如下：
Broker启动时向配置的所有NameServer发送心跳语句，每隔30秒发送一次，NameServer收到心跳之后，新建/更新BrokerLiveInfo对象，特别是BrokerLiveInfo的lastUpdateTimestamp属性，它标识着上次心跳是时间。NameServer每隔10秒钟会扫描brokerLiveTable集合，如果lastUpdateTimestamp时间超过120秒，NameServer将认为此Broker不可用，NameServer会移除此Broker的路由信息同时关闭Socket连接。
NameServer收到心跳后返回会话信息，通知Broker的类型是否为master
2.3.2.1 Broker发送心跳包
// BrokerController#start()
// 创建定时任务，延迟10秒，每30秒执行一次
// brokerConfig.getRegisterNameServerPeriod() = 30 * 1000 (milliseconds)
this.scheduledExecutorService.scheduleAtFixedRate(new Runnable() {
@Override
public void run() {
try {
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);
// BrokerController#registerBrokerAll
public synchronized void registerBrokerAll(final boolean checkOrderConfig, boolean oneway, boolean forceRegister) {
// ... ...
if (/*...*/) {
doRegisterBrokerAll(checkOrderConfig, oneway, topicConfigWrapper);
}
}
// BrokerController#doRegisterBrokerAll
private void doRegisterBrokerAll(boolean checkOrderConfig, boolean oneway,
TopicConfigSerializeWrapper topicConfigWrapper) {
List<RegisterBrokerResult> 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());
// ... ...
}
// BrokerOuterAPI#registerBrokerAll
public List<RegisterBrokerResult> registerBrokerAll(
final String clusterName,
final String brokerAddr,
final String brokerName,
final long brokerId,
final String haServerAddr,
final TopicConfigSerializeWrapper topicConfigWrapper,
final List<String> filterServerList,
final boolean oneway,
final int timeoutMills,
final boolean compressed) {
final List<RegisterBrokerResult> registerBrokerResultList = new CopyOnWriteArrayList<>();
List<String> nameServerAddressList = this.remotingClient.getNameServerAddressList();
if (nameServerAddressList != null && nameServerAddressList.size() > 0) {
// 设置统一的请求头信息
final RegisterBrokerRequestHeader requestHeader = new RegisterBrokerRequestHeader();
requestHeader.setBrokerAddr(brokerAddr); // Broker的IP地址
requestHeader.setBrokerId(brokerId); // Broker的ID，等于0:Master，大于0: Slave
requestHeader.setBrokerName(brokerName); // Broker名称
requestHeader.setClusterName(clusterName); // Broker所在集群名称
requestHeader.setHaServerAddr(haServerAddr); // Master的地址，第一次请求时为空，Slave向NameServer注册后返回
requestHeader.setCompressed(compressed);
RegisterBrokerBody requestBody = new RegisterBrokerBody(); // 消息服务器过滤列表
requestBody.setTopicConfigSerializeWrapper(topicConfigWrapper); // 主题配置，topicConfigWrapper内部封装的是TopicManager中的TopicCofigTable，内部存储的是Broker启动时的默认topic，MixAll.SELF_TEST_TOPIC、MixAll.DEFAULT_TOPIC(AutoCreateTopicEnable = true)、MixAll.BENCHMARK_TOPIC、MixAll.OFFSET_MOVED_EVENT、BrokerConfig#brokerClusterName、BrokerConfig#brokerName。Broker中，Topic的，默认存储位置：${Rocket_HOME}/store/config/topic.json中。
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());
// 遍历所有配置的NamerServer地址，使用countDownLatch保证所有线程结束后再继续执行
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", brokerId, namesrvAddr);
} catch (Exception e) {
log.warn("registerBroker Exception, {}", namesrvAddr, e);
} finally {
countDownLatch.countDown();
}
}
});
}
try {
// 计数到0时，继续执行
countDownLatch.await(timeoutMills, TimeUnit.MILLISECONDS);
} catch (InterruptedException e) {
}
}
return registerBrokerResultList;
}
// BrokerOuterAPI#registerBroker()
private RegisterBrokerResult registerBroker(
final String namesrvAddr,
final boolean oneway,
final int timeoutMills,
final RegisterBrokerRequestHeader requestHeader,
final byte[] body
) throws RemotingCommandException, MQBrokerException, RemotingConnectException, RemotingSendRequestException, RemotingTimeoutException,
InterruptedException {
RemotingCommand request = RemotingCommand.createRequestCommand(RequestCode.REGISTER_BROKER, requestHeader);
request.setBody(body);
// 如果是单向发送
if (oneway) {
try {
this.remotingClient.invokeOneway(namesrvAddr, request, timeoutMills);
} catch (RemotingTooMuchRequestException e) {
// Ignore
}
return null;
}
// 不是单向发送
RemotingCommand response = this.remotingClient.invokeSync(namesrvAddr, request, timeoutMills);
assert response != null;
switch (response.getCode()) {
case ResponseCode.SUCCESS: {
RegisterBrokerResponseHeader responseHeader =
(RegisterBrokerResponseHeader) response.decodeCommandCustomHeader(RegisterBrokerResponseHeader.class);
RegisterBrokerResult result = new RegisterBrokerResult();
result.setMasterAddr(responseHeader.getMasterAddr()); // 注册返回的主Broker，IP
result.setHaServerAddr(responseHeader.getHaServerAddr()); // 主Broker的地址， IP:Port
if (response.getBody() != null) {
result.setKvTable(KVTable.decode(response.getBody(), KVTable.class));
}
return result;
}
default:
break;
}
}
2.3.2.2 NameServer处理心跳包
// RouteInfoManager.java
public RegisterBrokerResult registerBroker(
final String clusterName,
final String brokerAddr,
final String brokerName,
final long brokerId,
final String haServerAddr,
final TopicConfigSerializeWrapper topicConfigWrapper,
final List<String> filterServerList,
final Channel channel) {
RegisterBrokerResult result = new RegisterBrokerResult();
try {
try {
// 路由注册需要加锁
this.lock.writeLock().lockInterruptibly();
// 维护 clusterAddrTable
Set<String> brokerNames = this.clusterAddrTable.get(clusterName);
// 先判断是否存在
if (null == brokerNames) {
// 不存在需要新建初始化
brokerNames = new HashSet<String>();
this.clusterAddrTable.put(clusterName, brokerNames);
}
brokerNames.add(brokerName);
// 是否第一次注册
boolean registerFirst = false;
// 维护 brokerAddrTable中的BrokerData信息
BrokerData brokerData = this.brokerAddrTable.get(brokerName);
if (null == brokerData) {
// 不存在这个broker的数据，说明是第一次注册，新建并放入brokerAddrTable中
registerFirst = true;
brokerData = new BrokerData(clusterName, brokerName, new HashMap<Long, String>());
this.brokerAddrTable.put(brokerName, brokerData);
}
Map<Long, String> brokerAddrsMap = brokerData.getBrokerAddrs();
//从Borker切换到主Broker：首先删除namesrv中的<1，IP:PORT>，然后添加<0，IP:PORT>
//同一 IP:PORT 在brokerAddrTable中只能有一条记录
Iterator<Entry<Long, String>> it = brokerAddrsMap.entrySet().iterator();
while (it.hasNext()) {
Entry<Long, String> item = it.next();
// 将 broker地址相同 + brokerId不同 的元素删除，地址相同、id相同就是跟以前一样的数据，不用修改
if (null != brokerAddr && brokerAddr.equals(item.getValue()) && brokerId != item.getKey()) {
it.remove();
}
}
String oldAddr = brokerData.getBrokerAddrs().put(brokerId, brokerAddr);
registerFirst = registerFirst || (null == oldAddr);
// 主Broker
if (null != topicConfigWrapper && MixAll.MASTER_ID == brokerId) {
// topic配置产生变化，或者第一次注册
if (this.isBrokerTopicConfigChanged(brokerAddr, topicConfigWrapper.getDataVersion())
|| registerFirst) {
ConcurrentMap<String, TopicConfig> tcTable = topicConfigWrapper.getTopicConfigTable();
if (tcTable != null) {
for (Map.Entry<String, TopicConfig> entry : tcTable.entrySet()) {
// 更新配置
this.createAndUpdateQueueData(brokerName, entry.getValue());
}
}
}
}
// 旧的Broker状态
BrokerLiveInfo prevBrokerLiveInfo = this.brokerLiveTable.put(brokerAddr,
new BrokerLiveInfo(
System.currentTimeMillis(), // 当前时间
topicConfigWrapper.getDataVersion(),
channel,
haServerAddr));
if (null == prevBrokerLiveInfo) {
log.info("new broker registered, {} HAServer: {}", brokerAddr, haServerAddr);
}
if (filterServerList != null) {
if (filterServerList.isEmpty()) {
this.filterServerTable.remove(brokerAddr);
} else {
this.filterServerTable.put(brokerAddr, filterServerList);
}
}
if (MixAll.MASTER_ID != brokerId) {
// 如果NameServer检测出是从Broker，需要获取master的地址，并将Master的地址返回给Broker
String masterAddr = brokerData.getBrokerAddrs().get(MixAll.MASTER_ID);
if (masterAddr != null) {
BrokerLiveInfo brokerLiveInfo = this.brokerLiveTable.get(masterAddr);
if (brokerLiveInfo != null) {
result.setHaServerAddr(brokerLiveInfo.getHaServerAddr());
result.setMasterAddr(masterAddr);
}
}
}
} finally {
this.lock.writeLock().unlock();
}
} catch (Exception e) {
log.error("registerBroker Exception", e);
}
return result;
}
2.3.3 路由删除
Brokers每30秒向NameServer发送心跳包，包括BrokerID，Broker地址，所属的集群名称，关联的FilterServer等
NameServer每10秒检查一次BrokerLiveInfo的lastUpdateTimestamp字段，距离当前时间超过120秒，则认为此Broker不可用，NameServer会移除此Broker的路由信息同时关闭Socket连接，并同时更新路由表：topicQueueTable、brokerAddrTable、brokerLiveTable、filterServerTable。
2.3.3.1 触发路由删除的两个触发点
-
当NameServer扫描所有Broker时，发现brokerLiveTable中Broker的上次心跳时间距离当前时间超过120秒
-
Broker在正常关闭的时候，会执行unregisterBroker()
两种触发方式虽然不同，但是删除路由的步骤是一样的：删除topicQueueTable、brokerAddrTable、brokerLiveTable、filterServerTable中相关的信息（移除路由信息），关闭Socket连接。
2.3.3.2 从超时120秒阅读源码
// NamesrvController#initialize
public boolean initialize() {
// ... ...
this.scheduledExecutorService.scheduleAtFixedRate(new Runnable() {
@Override
public void run() {
// NameServer初始化时定义的定时任务线程：扫描不可用的Broker
NamesrvController.this.routeInfoManager.scanNotActiveBroker();
}
}, 5, 10, TimeUnit.SECONDS);
// ... ...
}
// RouteInfoManager#scanNotActiveBroker
public void scanNotActiveBroker() {
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()) {
// 与当前时间比较，大于120秒，关闭Channel
RemotingUtil.closeChannel(next.getValue().getChannel());
it.remove();
log.warn("The broker channel expired, {} {}ms", next.getKey(), BROKER_CHANNEL_EXPIRED_TIME);
// 从topicQueueTable、brokerAddrTable、brokerLiveTable、filterServerTable移除Broker信息
this.onChannelDestroy(next.getKey(), next.getValue().getChannel());
}
}
}
// RouteInfoManager#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 {
// 加写锁，分别从brokerLiveTable、filterServerTable、brokerAddrTable、clusterAddrTable中清除Broker信息
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)) {
// NameServer底层数据结构要求，主从Broker配置文件名称一致
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();
// 当最底层的brokerAddr和需要删除的地址相同时，清除掉此地址
if (brokerAddr.equals(brokerAddrFound)) {
brokerNameFound = brokerData.getBrokerName();
it.remove();
log.info("remove brokerAddr[{}, {}] from brokerAddrTable, because channel destroyed",brokerId, brokerAddr);
break;
}
}
// 删除Broker之后不再存在节点信息时，修改属性
if (brokerData.getBrokerAddrs().isEmpty()) {
removeBrokerName = true;
itBrokerAddrTable.remove();
log.info("remove brokerName[{}] from brokerAddrTable, because channel destroyed",
brokerData.getBrokerName());
}
}
if (brokerNameFound != null && removeBrokerName) {
Iterator<Entry<String, Set<String>>> it = this.clusterAddrTable.entrySet().iterator();
while (it.hasNext()) {
Entry<String, Set<String>> entry = it.next();
String clusterName = entry.getKey();
Set<String> brokerNames = entry.getValue();
boolean removed = brokerNames.remove(brokerNameFound);
if (removed) {
log.info("remove brokerName[{}], clusterName[{}] from clusterAddrTable, because channel destroyed",brokerNameFound, clusterName);
// 如果移除后，集群内不包含任何Broker，则将该集群从clusterAddrTable中移除
if (brokerNames.isEmpty()) {
log.info("remove the clusterName[{}] from clusterAddrTable, because channel destroyed and no broker in this cluster",clusterName);
it.remove();
}
break;
}
}
}
if (removeBrokerName) {
Iterator<Entry<String, List<QueueData>>> itTopicQueueTable =
this.topicQueueTable.entrySet().iterator();
while (itTopicQueueTable.hasNext()) {
Entry<String, List<QueueData>> entry = itTopicQueueTable.next();
String topic = entry.getKey();
List<QueueData> queueDataList = entry.getValue();
Iterator<QueueData> itQueueData = queueDataList.iterator();
while (itQueueData.hasNext()) {
QueueData queueData = itQueueData.next();
// 从topicQueueTable中删除broker相关的QueueData
if (queueData.getBrokerName().equals(brokerNameFound)) {
itQueueData.remove();
log.info("remove topic[{} {}], from topicQueueTable, because channel destroyed", topic, queueData);
}
}
// 队列为空，直接清除
if (queueDataList.isEmpty()) {
itTopicQueueTable.remove();
log.info("remove topic[{}] all queue, from topicQueueTable, because channel destroyed",topic);
}
}
}
} finally {
// 释放写锁，删除路由完成
this.lock.writeLock().unlock();
}
} catch (Exception e) {
log.error("onChannelDestroy Exception", e);
}
}
}
- 其中topicQueueTable，brokerAddrTable、clusterAddrTable都需要两次遍历才能获取到brokerAddr，而brokerLiveTable、filterServerTable两个的HashMap的主键就是bokerName，所以可以不用遍历直接remove()。
- 获取brokerAddrFound的时候使用的可中断读锁，维护路由表的时候使用了可中断的写锁。
2.3.4 路由发现
总体流程： 通过RouteInfoManager#pickupTopicRouteData()根据topic查找路由信息，然后判断是否为顺序消息，是的话加载顺序消息配置
// DefaultRequestProcessor
public RemotingCommand getRouteInfoByTopic(ChannelHandlerContext ctx, RemotingCommand request) throws RemotingCommandException {
final RemotingCommand response = RemotingCommand.createResponseCommand(null);
final GetRouteInfoRequestHeader requestHeader = (GetRouteInfoRequestHeader) request
.decodeCommandCustomHeader(GetRouteInfoRequestHeader.class);
// 调用RouteInfoManager#pickupTopicRouteData()，分别填充TopicRouteData中的以下字段
// List<QueueData> queueDatas;
// List<BrokerData> brokerDatas;
// HashMap<String/* brokerAddr */, List<String>/* Filter Server */> filterServerTable
TopicRouteData topicRouteData = this.namesrvController.getRouteInfoManager()
.pickupTopicRouteData(requestHeader.getTopic());
if (topicRouteData != null) {
// 判断该主题是否时是顺序消息
if (this.namesrvController.getNamesrvConfig().isOrderMessageEnable()) {
// 从NameserverKVconfig中获取顺序消息相关配置
String orderTopicConf = this.namesrvController.getKvConfigManager()
.getKVConfig(NamesrvUtil.NAMESPACE_ORDER_TOPIC_CONFIG,requestHeader.getTopic());
topicRouteData.setOrderTopicConf(orderTopicConf);
}
byte[] content = topicRouteData.encode();
response.setBody(content);
response.setCode(ResponseCode.SUCCESS);
response.setRemark(null);
return response;
}
// 没有找到返回 ResponseCode.TOPIC_NOT_EXIST：17
response.setCode(ResponseCode.TOPIC_NOT_EXIST);
response.setRemark("No topic route info in name server for the topic: " + requestHeader.getTopic()
+ FAQUrl.suggestTodo(FAQUrl.APPLY_TOPIC_URL));
return response;
}
// RouteInfoManager
public TopicRouteData pickupTopicRouteData(final String topic) {
TopicRouteData topicRouteData = new TopicRouteData();
boolean foundQueueData = false;
boolean foundBrokerData = false;
Set<String> brokerNameSet = new HashSet<String>();
List<BrokerData> brokerDataList = new LinkedList<BrokerData>();
topicRouteData.setBrokerDatas(brokerDataList);
HashMap<String, List<String>> filterServerMap = new HashMap<String, List<String>>();
topicRouteData.setFilterServerTable(filterServerMap);
try {
try {
// 可中断读锁
this.lock.readLock().lockInterruptibly();
// QueueData的属性：brokerName
List<QueueData> queueDataList = this.topicQueueTable.get(topic);
if (queueDataList != null) {
topicRouteData.setQueueDatas(queueDataList);
foundQueueData = true;
// 收集 brokerName 到set集合
Iterator<QueueData> it = queueDataList.iterator();
while (it.hasNext()) {
QueueData qd = it.next();
brokerNameSet.add(qd.getBrokerName());
}
// 根据 brokerName 到brokerAddrTable中获取BrokerData，从而得到brokerAddr和FilterServer的关系
for (String brokerName : brokerNameSet) {
BrokerData brokerData = this.brokerAddrTable.get(brokerName);
if (null != brokerData) {
BrokerData brokerDataClone = new BrokerData(brokerData.getCluster(), brokerData.getBrokerName(), (HashMap<Long, String>) brokerData.getBrokerAddrs().clone());
brokerDataList.add(brokerDataClone);
foundBrokerData = true;
for (final String brokerAddr : brokerDataClone.getBrokerAddrs().values()) {
// 获取brokerAddr关联的过滤器Filter Server
List<String> filterServerList = this.filterServerTable.get(brokerAddr);
filterServerMap.put(brokerAddr, filterServerList);
}
}
}
}
} finally {
this.lock.readLock().unlock();
}
} catch (Exception e) {
log.error("pickupTopicRouteData Exception", e);
}
log.debug("pickupTopicRouteData {} {}", topic, topicRouteData);
if (foundBrokerData && foundQueueData) {
return topicRouteData;
}
return null;
}
340
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
