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 bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
any
RocketMQ version
develop
JDK Version
any
Describe the Bug
Lmq msg's queueOffset field is set to 0 wrongly. Easy to reproduce. Actually I found following codes in MessageExtEncoder.java:
But the latter update of queueOffset was not found.
Steps to Reproduce
Run a broker under latest develop version.
Send msgs and set Lmq related properties.
The queueOffset of these msgs is zero.
What Did You Expect to See?
Correct queueOffset.
What Did You See Instead?
Zero queueOffset.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
I found the update code in CommitLog.java
But it seems that DLedgerCommitLog doesn't support LMQ for now, I'll change this issue's title and commit another pr later.
bxfjb
changed the title
[Bug] Lmq msg queueOffset is set to 0 wrongly
[Bug] DLedger doesn't support LMQ
Nov 15, 2024
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
any
RocketMQ version
develop
JDK Version
any
Describe the Bug
Lmq msg's queueOffset field is set to 0 wrongly. Easy to reproduce. Actually I found following codes in
MessageExtEncoder.java
:But the latter update of queueOffset was not found.
Steps to Reproduce
Run a broker under latest develop version.
Send msgs and set Lmq related properties.
The queueOffset of these msgs is zero.
What Did You Expect to See?
Correct queueOffset.
What Did You See Instead?
Zero queueOffset.
Additional Context
No response
The text was updated successfully, but these errors were encountered: