consumer return RECONSUME_LATER but not get retry message

[garnett10330]

QAQ help me Why my consumer return RECONSUME_LATER but no get retry message;
but same code in my friend's computer can get retry message

[RongtongJin]

Could you tell me which version you are using? it seems there is no issue with the latest version in my environment.

[RongtongJin]

I will close the Issue first, but please feel free to reopen it if you have any other issues.

[garnett10330]

V4_3_0 and V4_7_0 all have this question

[garnett10330]

Have any properties can control not retry message ?
In my computer I try 3 version all have this question
but in my friend's computer can retry
his computer's rocketmq version is same as me
why?

[spiritsx]

we encounter this question too，the rocketmq version is 4.5.1。
But when we install the version to another server，the question goes away，interesting。
Did you slove it?

[spiritsx]

we encounter this question too，the rocketmq version is 4.5.1。
But when we install the version to another server，the question goes away，interesting。
Did you slove it?

After two day later, we sloved it。
The question is about delayOffset.json。As you know，the broker process persist SCHEDULE_TOPIC_XXXX offset to delayOffset.json。When we drop the store folder，we didn't noticed it generate a store/config folder automatic by broker。Whereafter，we reset broker，but the offset from delayOffset not matched the offset from SCHEDULE_TOPIC_XXXX，so the message in SCHEDULE_TOPIC_XXXX cannot enter %RETRY% topic。

[garnett10330]

Thank for your explanation
I do not slove it
How can i do to sloved the problem
Drop store folder and Reinstall rocketMq?

[spiritsx]

No need to reinstall, just to stop broker, drop store folder, and then start broker。Actually, you can check the rocketmq log, find that are there warn log like "Offset not matched. Request offset"。The relevant logic you can find from ScheduleMessageService 271 line。 Wish it helpful to you 

[joytom0591]

I just encounter this question, but I'm not sure if they are the same question:
1、consumeGroup=ORDER-CONFIRM receive A Message TOPIC = "TDTP" key = "5279213024614400", After consume fail, the code "return ConsumeConcurrentlyStatus.RECONSUME_LATER;", but not receive retry any more.
2、on the MQ console, use condition TOPIC = "RETRY%ORDER-CONFIRM" and key = "5279213024614400" , can't find this message
3、on the MQ console, use condition TOPIC = "TDTP" and key = "5279213024614400", find this message, and this message was marked "CONSUMED"

before encounter this question, I upgrade rocketmq 4.1.x to 4.3.2,
1、 I install rocketmq-4.3.2 to anther directory,
2、 stop old rocketmq-4.1.x
3、move rocketmq-4.1.x/store to rocketmq-4.3.2/store(the path configured in broker-x.properties)
4、start rocketmq-4.3.2

Are they the same question? @spiritsx

[spiritsx]

sounds the same question, you can check the rocketmq log, find that are there warn log like "Offset not matched. Request offset".

[joytom0591]

question

Yes, there are many log like this, and at the same time the message consume fail, the rocketmq had one log:
"storeerror.log:2021-02-06 16:26:28 WARN FlushConsumeQueueService - Offset not matched. Request offset: 354000000, firstOffset: 348000000, lastOffset: 354000000, mappedFileSize: 6000000, mappedFiles count: 1"

How to solve this problem without loss of messages (do not drop store folder), upgrade to newest version? @spiritsx