When subscribing to a RocketMQ consumer group, EventMesh runtime didn't update the Queue Consumer Offset properly. This is causing the RocketMQ Queue Consumer Offset is not in sync with the actual number of messages already consumed.
After the EventMesh runtime restarted, the already consumed messages get pushed again to the Client Subscribers. This is causing duplicated messages being consumed.
From the RocketMQ Console (installed from here: https://github.com/apache/rocketmq-externals/tree/master/rocketmq-console), I observed the some Queue Consumer Offsets are not updated, even after all messages are consumed by the Client Subscriber.

Actual Offset Result:

Expected Offset Result:
