RocketMQ源码解析六（Consumer重平衡流程）

心已赠人 2022-09-12 07:47 3阅读 0赞

RocketMQ版本4.6.0，记录自己看源码的过程

重平衡服务是在Consumer启动的时候启动的一个后台线程，每次重平衡后过20s后再发起一次重平衡

  1. /** * 重平衡服务，随着consumer启动而启动 */
  3. public class RebalanceService extends ServiceThread { 
  4.     private static long waitInterval =
  5.         Long.parseLong(System.getProperty(
  6.             "rocketmq.client.rebalance.waitInterval", "20000"));
  7.     private final InternalLogger log = ClientLogger.getLog();
  8.     private final MQClientInstance mqClientFactory;
  10.     public RebalanceService(MQClientInstance mqClientFactory) { 
  11.         this.mqClientFactory = mqClientFactory;
  12.     }
  14.     @Override
  15.     public void run() { 
  16.         log.info(this.getServiceName() + " service started");
  18.         while (!this.isStopped()) { 
  19.             // 每20s执行一次
  20.             this.waitForRunning(waitInterval);
  21.             this.mqClientFactory.doRebalance();
  22.         }
  24.         log.info(this.getServiceName() + " service end");
  25.     }
  27.     @Override
  28.     public String getServiceName() { 
  29.         return RebalanceService.class.getSimpleName();
  30.     }
  31. }

MQClientInstance

  1. /** * 重平衡 */
  2. public void doRebalance() { 
  3.     // 遍历每个消费组的消费者实例
  4.     for (Map.Entry<String, MQConsumerInner> entry : this.consumerTable.entrySet()) { 
  5.         MQConsumerInner impl = entry.getValue();
  6.         if (impl != null) { 
  7.             try { 
  8.                 impl.doRebalance();
  9.             } catch (Throwable e) { 
  10.                 log.error("doRebalance exception", e);
  11.             }
  12.         }
  13.     }
  14. }

DefaultMQPushConsumerImpl

  1. @Override
  2. public void doRebalance() { 
  3.     if (!this.pause) { 
  4.         // 调用重平衡组件
  5.         this.rebalanceImpl.doRebalance(this.isConsumeOrderly());
  6.     }
  7. }

调用重平衡组件RebalanceImpl进行重平衡逻辑

  1. public abstract class RebalanceImpl { 
  2.     protected static final InternalLogger log = ClientLogger.getLog();
  3.     // 当前消费者分配到的队列
  4.     protected final ConcurrentMap<MessageQueue, ProcessQueue> processQueueTable = new ConcurrentHashMap<MessageQueue, ProcessQueue>(64);
  5.     // 保存所订阅的每个主题中的消息队列列表
  6.     protected final ConcurrentMap<String/* topic */, Set<MessageQueue>> topicSubscribeInfoTable =
  7.         new ConcurrentHashMap<String, Set<MessageQueue>>();
  8.     /** * 订阅数据，由于一个消费者可以订阅多个topic，所以这里的订阅数据用map类型 * key是订阅的topic名称，value其实也只是topic名称外加其它一些东西 */
  9.     protected final ConcurrentMap<String /* topic */, SubscriptionData> subscriptionInner =
  10.         new ConcurrentHashMap<String, SubscriptionData>();
  11.     protected String consumerGroup;
  12.     /** * 消费模式 */
  13.     protected MessageModel messageModel;
  14.     /** * 负载策略，默认是平均算法 */
  15.     protected AllocateMessageQueueStrategy allocateMessageQueueStrategy;
  16.     protected MQClientInstance mQClientFactory;
  18.     /** * 开始执行重平衡逻辑 * * @param isOrder 是否是顺序消费 */
  19.     public void doRebalance(final boolean isOrder) { 
  20.         Map<String, SubscriptionData> subTable = this.getSubscriptionInner();
  21.         if (subTable != null) { 
  22.             // 遍历订阅的每个topic，对每个topic中的队列都重新负载均衡
  23.             for (final Map.Entry<String, SubscriptionData> entry : subTable.entrySet()) { 
  24.                 final String topic = entry.getKey();
  25.                 try { 
  26.                     this.rebalanceByTopic(topic, isOrder);
  27.                 } catch (Throwable e) { 
  28.                     if (!topic.startsWith(MixAll.RETRY_GROUP_TOPIC_PREFIX)) { 
  29.                         log.warn("rebalanceByTopic Exception", e);
  30.                     }
  31.                 }
  32.             }
  33.         }
  35.         this.truncateMessageQueueNotMyTopic();
  36.     }
  38.     /** * 根据topic对其中的队列进行重平衡 */
  39.     private void rebalanceByTopic(final String topic, final boolean isOrder) { 
  40.         switch (messageModel) { 
  41.             case BROADCASTING: { 
  42.                 Set<MessageQueue> mqSet = this.topicSubscribeInfoTable.get(topic);
  43.                 if (mqSet != null) { 
  44.                     boolean changed = this.updateProcessQueueTableInRebalance(topic, mqSet, isOrder);
  45.                     if (changed) { 
  46.                         this.messageQueueChanged(topic, mqSet, mqSet);
  47.                         log.info("messageQueueChanged {} {} {} {}",
  48.                             consumerGroup,
  49.                             topic,
  50.                             mqSet,
  51.                             mqSet);
  52.                     }
  53.                 } else { 
  54.                     log.warn("doRebalance, {}, but the topic[{}] not exist.", consumerGroup, topic);
  55.                 }
  56.                 break;
  57.             }
  58.             // 集群模式
  59.             case CLUSTERING: { 
  60.                 // 该topic对应的消息队列
  61.                 Set<MessageQueue> mqSet = this.topicSubscribeInfoTable.get(topic);
  62.                 // 从随机的一个broker中获取该消费组中所有的消费者客户端ID
  63.                 List<String> cidAll = this.mQClientFactory.findConsumerIdList(topic, consumerGroup);
  64.                 if (null == mqSet) { 
  65.                     if (!topic.startsWith(MixAll.RETRY_GROUP_TOPIC_PREFIX)) { 
  66.                         log.warn("doRebalance, {}, but the topic[{}] not exist.", consumerGroup, topic);
  67.                     }
  68.                 }
  70.                 if (null == cidAll) { 
  71.                     log.warn("doRebalance, {} {}, get consumer id list failed", consumerGroup, topic);
  72.                 }
  74.                 // 如果有一个为空，则放弃本次负载均衡
  75.                 if (mqSet != null && cidAll != null) { 
  76.                     List<MessageQueue> mqAll = new ArrayList<MessageQueue>();
  77.                     // 将消息队列从Set中复制到List中
  78.                     mqAll.addAll(mqSet);
  79.                     // 对消息队列和消费者客户端id排序，这样可以保证每个消费者重平衡时队列顺序一样，就不会有重复分配问题
  80.                     Collections.sort(mqAll);
  81.                     Collections.sort(cidAll);
  83.                     AllocateMessageQueueStrategy strategy = this.allocateMessageQueueStrategy;
  85.                     // 分配给该消费者的队列
  86.                     List<MessageQueue> allocateResult = null;
  87.                     try { 
  88.                         // 根据负载均衡策略重平衡
  89.                         allocateResult = strategy.allocate(
  90.                             this.consumerGroup,
  91.                             this.mQClientFactory.getClientId(),
  92.                             mqAll,
  93.                             cidAll);
  94.                     } catch (Throwable e) { 
  95.                         log.error("AllocateMessageQueueStrategy.allocate Exception. allocateMessageQueueStrategyName={}", strategy.getName(),
  96.                             e);
  97.                         return;
  98.                     }
  100.                     Set<MessageQueue> allocateResultSet = new HashSet<MessageQueue>();
  101.                     if (allocateResult != null) { 
  102.                         allocateResultSet.addAll(allocateResult);
  103.                     }
  105.                     // 判断该消费者的订阅的队列是否有变
  106.                     // 如果是顺序消费，还会对消费队列进行加解锁
  107.                     boolean changed = this.updateProcessQueueTableInRebalance(topic, allocateResultSet, isOrder);
  108.                     if (changed) { 
  109.                         log.info(
  110.                             "rebalanced result changed. allocateMessageQueueStrategyName={}, group={}, topic={}, clientId={}, mqAllSize={}, cidAllSize={}, rebalanceResultSize={}, rebalanceResultSet={}",
  111.                             strategy.getName(), consumerGroup, topic, this.mQClientFactory.getClientId(), mqSet.size(), cidAll.size(),
  112.                             allocateResultSet.size(), allocateResultSet);
  113.                         // 更改后需要立即发送心跳通知所有的broker
  114.                         this.messageQueueChanged(topic, mqSet, allocateResultSet);
  115.                     }
  116.                 }
  117.                 break;
  118.             }
  119.             default:
  120.                 break;
  121.         }
  122.     }
  124.     /** * 判断订阅的队列是否有变 * */
  125.     private boolean updateProcessQueueTableInRebalance(final String topic, final Set<MessageQueue> mqSet,
  126.         final boolean isOrder) { 
  127.         boolean changed = false;
  129.         // 当前消费者已经分配到的消息队列
  130.         Iterator<Entry<MessageQueue, ProcessQueue>> it = this.processQueueTable.entrySet().iterator();
  131.         while (it.hasNext()) { 
  132.             Entry<MessageQueue, ProcessQueue> next = it.next();
  133.             MessageQueue mq = next.getKey();
  134.             ProcessQueue pq = next.getValue();
  136.             // 不属于该topic的队列跳过
  137.             if (mq.getTopic().equals(topic)) { 
  138.                 // 如果重新分配后的队列不包含旧的队列mq，说明经过重平衡后，该队列被分配给别的消费者了，
  139.                 // 所以需要暂停当前消费者对该队列的消费，将该ProcessQueue设置dropped=true，并从本地缓存中移除
  140.                 if (!mqSet.contains(mq)) { 
  141.                     pq.setDropped(true);
  142.                     if (this.removeUnnecessaryMessageQueue(mq, pq)) { 
  143.                         // 从订阅缓存中移除该队列
  144.                         it.remove();
  145.                         changed = true;
  146.                         log.info("doRebalance, {}, remove unnecessary mq, {}", consumerGroup, mq);
  147.                     }
  148.                 } else if (pq.isPullExpired()) { 
  149.                     switch (this.consumeType()) { 
  150.                         case CONSUME_ACTIVELY:
  151.                             break;
  152.                         case CONSUME_PASSIVELY:
  153.                             pq.setDropped(true);
  154.                             if (this.removeUnnecessaryMessageQueue(mq, pq)) { 
  155.                                 it.remove();
  156.                                 changed = true;
  157.                                 log.error("[BUG]doRebalance, {}, remove unnecessary mq, {}, because pull is pause, so try to fixed it",
  158.                                     consumerGroup, mq);
  159.                             }
  160.                             break;
  161.                         default:
  162.                             break;
  163.                     }
  164.                 }
  165.             }
  166.         }
  168.         List<PullRequest> pullRequestList = new ArrayList<PullRequest>();
  169.         for (MessageQueue mq : mqSet) { 
  170.             // 如果旧的缓存订阅的队列中没有新的队列，说明经过重平衡后，该消费者分配到了新的队列
  171.             // 则需要创建PullRequest拉取消息任务去拉取消息
  172.             if (!this.processQueueTable.containsKey(mq)) { 
  173.                 // 这里在顺序消费那里详细讲解
  174.                 if (isOrder && !this.lock(mq)) { 
  175.                     log.warn("doRebalance, {}, add a new mq failed, {}, because lock failed", consumerGroup, mq);
  176.                     continue;
  177.                 }
  179.                 // 从内存中删除该消息队列的消费进度
  180.                 this.removeDirtyOffset(mq);
  181.                 // 创建一个新的ProcessQueue与该消息队列对应
  182.                 ProcessQueue pq = new ProcessQueue();
  183.                 // 计算从哪开始拉取
  184.                 long nextOffset = this.computePullFromWhere(mq);
  185.                 if (nextOffset >= 0) { 
  186.                     ProcessQueue pre = this.processQueueTable.putIfAbsent(mq, pq);
  187.                     if (pre != null) { 
  188.                         log.info("doRebalance, {}, mq already exists, {}", consumerGroup, mq);
  189.                     } else { 
  190.                         log.info("doRebalance, {}, add a new mq, {}", consumerGroup, mq);
  191.                         PullRequest pullRequest = new PullRequest();
  192.                         pullRequest.setConsumerGroup(consumerGroup);
  193.                         pullRequest.setNextOffset(nextOffset);
  194.                         pullRequest.setMessageQueue(mq);
  195.                         pullRequest.setProcessQueue(pq);
  196.                         pullRequestList.add(pullRequest);
  197.                         changed = true;
  198.                     }
  199.                 } else { 
  200.                     log.warn("doRebalance, {}, add new mq failed, {}", consumerGroup, mq);
  201.                 }
  202.             }
  203.         }
  205.         // 立即去执行拉取任务，其实就是将拉取请求任务放到拉取请求队列中
  206.         this.dispatchPullRequest(pullRequestList);
  208.         return changed;
  209.     }
  210. }

重平衡详细流程都写在注释里了，参考注释。
最终是为所分配到新的消费队列创建一个拉取请求任务放到拉取任务阻塞队列中，这样消费者就可以开始拉取该消息队列的消息了。拉取任务只在这一处创建。
在这里插入图片描述

参考资料
《儒猿技术窝——从 0 开始带你成为消息中间件实战高手》

发表评论

表情：
评论列表 （有 0 条评论，3人围观）

还没有评论，来说两句吧...

相关阅读