-
Notifications
You must be signed in to change notification settings - Fork 907
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.
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
Bookie ledger replication error lead to increased disk usage #1908
Comments
@codelipenghui thank you for reporting this. I think there are two problems behind this issue.
I think the disk usage kept growing because replication worker keeps trying to replicate fragments but fail at the last 4 entries. when replication worker keeps doing that, it is writing entries again and again. so the disk usage is going up. this can be resolved when we fix #1066 for the second problem, it is an interesting problem. my guess is it is related to ledger metadata update during closing. but I have to take a deeper look before coming to any conclusions. |
would like to put it into 4.11 |
Faced this issue in our 3-node setup, but it is always the same 1 node that faced this problem. Pulsar 2.10.1 How can I fix the issue? |
This is what found in logs Bookie
broker
|
Any update on this issue? I encountered the same error. Pulsar-2.10.1 Thanks. |
BUG REPORT
Problem happens after reboot bookie(Bare metal), i can't remember a little bit about the detailed steps at the time.
Found that disk usage continued growth:
Then check the bookie log, found some ledger replicate error log:
This won't always happen, I also restarted bookie before.
I don't know why lost these four entries[E4139 - E4144] in bookie and ledger.
And this is dangerous that ledger replicate so many times.
After we disable autorecovery and find the topic use this ledger, then delete the topic,
entry log was successfully cleaned up
The text was updated successfully, but these errors were encountered: