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

fix committedIndex after truncate #316

Closed
yuz10 opened this issue Feb 22, 2024 · 1 comment
Closed

fix committedIndex after truncate #316

yuz10 opened this issue Feb 22, 2024 · 1 comment

Comments

@yuz10
Copy link
Contributor

yuz10 commented Feb 22, 2024

if the log is truncated, committedIndex may be greater than ledgerEndIndex, then if the member is selected as leader, the rocketmq cluster is down, because rocketmq cluster leader must be equal:
image

the leader log:
D1
image

the followers log:
D2
image
D0
image

the leader memery:
image

image
yuz10 added a commit to yuz10/dledger that referenced this issue Feb 22, 2024
@yuz10
[ISSUE openmessaging#316] fix committedIndex after truncate
c89b06d
@yuz10 yuz10 mentioned this issue Feb 22, 2024
Closed
@yuz10
Copy link
Contributor Author

yuz10 commented Feb 22, 2024 •
edited
Loading

The issue is fixed in https://github.com/openmessaging/dledger/pull/298/files#diff-6cf5583d627323d72dc7448eb1b6cabbe7dddbc4503118c2a05871f7a767b7efR991

image

@yuz10 yuz10 closed this as completed Feb 26, 2024
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.

[ISSUE #316] fix committedIndex after truncate yuz10/dledger
1 participant
@yuz10