Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] DLedgerCommitLog recover should use BufferSize not MsgSize #9084

Open
3 tasks done
bxfjb opened this issue Dec 26, 2024 · 0 comments · May be fixed by #9085
Open
3 tasks done

[Bug] DLedgerCommitLog recover should use BufferSize not MsgSize #9084

bxfjb opened this issue Dec 26, 2024 · 0 comments · May be fixed by #9085

Comments

@bxfjb
Copy link
Contributor

bxfjb commented Dec 26, 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

No response

Describe the Bug

dledgerRecoverAbnormally should use dispatchRequest.getBufferSize() not dispatchRequest.getMsgSize()

Steps to Reproduce

Kill broker process and recover it.

What Did You Expect to See?

processOffset is equal with max offset.

What Did You See Instead?

the processOffset in log should be much smaller than expected.

Additional Context

No response
@bxfjb bxfjb linked a pull request Dec 26, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix use bufferSize not msgSize in dledger recover bxfjb/rocketmq
1 participant
@bxfjb