问题描述
在我们项目开发工程中,用到消息队列rocketmq会出现顺序消费情况,比如我们做订单,整个订单流程是
1.创建订单 2.付款 3.订单完成(大概这样的流程)
但是我们整个流程如果通过队列形式去消费,我们就需要按照123这样的顺序去消费,刚开始接触rocketmq介绍会说,rocketmq本身就可以顺序消费啊,为啥还要强调顺序消费?
答:RocketMQ可以严格的保证消息有序。但这个顺序,不是全局顺序,只是分区(queue)顺序。要全局顺序只能一个分区。
(简单地说:我们发送到topic是相同,本身顺序是相同topic下的queue是轮训是消费,所以是顺序消费,但是我们需要将123顺序放入到一个queue中)默认情况下rocketmq中的topic有4个queue
如果解释:
而消费端消费的时候,是会分配到多个queue的,多个queue是同时拉取提交消费
解决思路
我们将每笔订单都要放入相同topic下的相同queue中
代码解释
pom.xml
<dependency>
<groupId>org.apache.rocketmq</groupId>
<artifactId>rocketmq-spring-boot-starter</artifactId>
<version>2.0.4</version>
</dependency>
application.properties(配置文件,rocketmq如何虚拟机集群部署,可以看上一个博客哦)
rocketmq.name-server:192.168.95.130:9876;192.168.95.131:9876;192.168.95.132:9876;192.168.95.133:9876
rocketmq.producer.group:testgroup
rocketmq.producer.send-msg-timeout:5000
rocketmq.producer.retry-times-when-send-failed:2
rocketmq.producer.max-message-size:4194304
rocketMQ消费者代码,我是用注解监听方式来消费的(这里主要是设置消费模式consumeMode = ConsumeMode.ORDERLY(Receive asynchronously delivered messages orderly. one queue, one thread),默认情况下是并发消费模式(ConsumeMode.CONCURRENTLY))
package com.example.test.config.rocketMq;
import org.apache.rocketmq.spring.annotation.ConsumeMode;
import org.apache.rocketmq.spring.annotation.RocketMQMessageListener;
import org.apache.rocketmq.spring.core.RocketMQListener;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.stereotype.Component;
/**
* @description: TODO
* @author: Lucf
* @create: 2020-07-31 15:26
*/
@Component
@RocketMQMessageListener(topic = "topic-lcf1", selectorExpression = "tag1", consumerGroup = "luchunfeng1",consumeMode = ConsumeMode.ORDERLY)
public class Consumer implements RocketMQListener<String> {
private static final Logger logger = LoggerFactory.getLogger(Consumer.class);
@Override
public void onMessage(String s) {
logger.info(s);
}
}
rocketMq生产者
package com.example.test.systemmo.controller;
import org.apache.rocketmq.client.producer.MessageQueueSelector;
import org.apache.rocketmq.client.producer.SendResult;
import org.apache.rocketmq.common.message.Message;
import org.apache.rocketmq.common.message.MessageQueue;
import org.apache.rocketmq.spring.core.RocketMQTemplate;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
import java.util.ArrayList;
import java.util.List;
/**
* @description: TODO
* @author: Lucf
* @create: 2020-07-31 15:33
*/
@RestController
@RequestMapping("/rocketmq")
public class mqSendController {
@Autowired
private RocketMQTemplate rocketMQTemplate;
@RequestMapping("/send/message/{tag}")
public String sendMessage(@PathVariable("tag") String tag) {
//顺序消费通过hashKey来确定他们在哪个queue
for(int i=0;i<100;i++){
rocketMQTemplate.syncSendOrderly("topic-lcf1:" + tag,"order:"+String.valueOf(i),"order");
}
//顺序消费通过hashKey来确定他们在哪个queue
for(int i=0;i<100;i++){
rocketMQTemplate.syncSendOrderly("topic-lcf1:" + tag,"orderOne:"+String.valueOf(i),"orderOne");
}
//正常发送消费
for(int i=0;i<100;i++){
rocketMQTemplate.convertAndSend("topic-lcf1:" + tag, "order:"+String.valueOf(i));
}
return "success";
}
}
我们来看下发送结果我们通过两个hashKey区别下当前所有的发送在一个queue中
结果:可以看出来都是有顺序的消费
我们来看下不用顺序消费:
结果:
到这里就结束了。可以清楚看出来,最终的顺序与不顺序消费,其实顺序消费有很多种方式,也可以通过取出queue数量根据你的orderid进行取余来发送到哪个queue中,都可以实现顺序消费!!!