yejiahao opened a new issue #2279:
URL: https://github.com/apache/rocketmq/issues/2279
In my case, a strange phenomenon happens reported by ***tester engineer***:
**comsumer scheduleMessageOffset > producer scheduleMessageOffset**
- RocketMQ version is **V4.5.2** (Both client API and Server)
- broker status
```
sh /home/rocketMQ/rocketmq-4.5.2/bin/mqadmin brokerStatus -b <IP:PORT>
...sh
bootTimestamp : 1598590974120
brokerVersion : 317
brokerVersionDesc : V4_5_2
commitLogDirCapacity : Total : 258.2 GiB, Free : 130.9 GiB.
...
runtime : [ 2 days, 23 hours, 56 minutes, 36 seconds
]
scheduleMessageOffset_1 : 138699,447
scheduleMessageOffset_16 : 2,0
scheduleMessageOffset_2 : 5559,28
scheduleMessageOffset_3 : 538,4
scheduleMessageOffset_4 : 3,0
...
```
- producer client sample
```java
Message msg = new Message("topic", "tag",
"body".getBytes(RemotingHelper.DEFAULT_CHARSET));
// 设置延迟消费级别
msg.setDelayTimeLevel(1);
// 等待存储完成后返回
msg.setWaitStoreMsgOK(true);
SendResult sendResult = producer.send(msg);
```
### Tester have restarted producer, consumer and rocketmq processor several
times.
Because of scheduleMessageOffset overflow (@see mqadmin result), all of the
producer which has **setDelayTimeLevel ** cannot produce message in target
topic, unless delay queue offset equals, e.g. ```scheduleMessageOffset_1
: 200,200```
Please feel free to contact. Thanks for your information.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
