You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
The INNER_MULTI_QUEUE_OFFSET of LMQ messages may be not continuous. As shown in the screenshot, "1075474,1075481,1075481" is skipped. By checking the commitlog, we found that this offset is occupied by one RETRY message but is not dispatched to LMQ cq in the end.
Store error logs when this issue occurs:
Motivation
Make sure the LMQ logic queue order is correct.
Describe the Solution You'd Like
When appending commitlog, do not allocate LMQ offset for messages of system topics, be consistent with consume queue dispath logic.
Describe Alternatives You've Considered
/
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
The INNER_MULTI_QUEUE_OFFSET of LMQ messages may be not continuous. As shown in the screenshot, "1075474,1075481,1075481" is skipped. By checking the commitlog, we found that this offset is occupied by one RETRY message but is not dispatched to LMQ cq in the end.
Store error logs when this issue occurs:
Motivation
Make sure the LMQ logic queue order is correct.
Describe the Solution You'd Like
When appending commitlog, do not allocate LMQ offset for messages of system topics, be consistent with consume queue dispath logic.
Describe Alternatives You've Considered
/
Additional Context
No response
The text was updated successfully, but these errors were encountered: