You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "fretory (via GitHub)" <gi...@apache.org> on 2025/08/15 06:44:02 UTC
Re: [I] [Bug]Pulsar 3.0.5 Topic service unavailable due to broken ledger in __change_events system topic [pulsar]
fretory commented on issue #24436:
URL: https://github.com/apache/pulsar/issues/24436#issuecomment-3190777196
> [Pulsar 3.0.13 release](https://pulsar.apache.org/release-notes/versioned/pulsar-3.0.13/) and [Pulsar 4.0.6 release](https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.6/) are now available with [BookKeeper 4.16.7 and 4.17.2](https://bookkeeper.apache.org/release-notes/) which includes a fix [apache/bookkeeper#4607](https://github.com/apache/bookkeeper/pull/4607).
Thanks for the update. I have some reservations about this being the root cause. I've been running the test code from that issue continuously for the past four days and haven't been able to reproduce the problem once.
I doubt this would corrupt the data and cause it to be subsequently cleaned up by the BookKeeper garbage collection thread.
```
// you
@org.junit.jupiter.api.Test
public void test() throws InterruptedException {
byte[] bytes = new byte[1024];
while (true) {
var buf = Unpooled.buffer(1024);
buf.writerIndex(1024);
if (ByteBufUtil.compare(buf, Unpooled.wrappedBuffer(bytes)) != 0) {
System.out.println(ByteBufUtil.hexDump(buf));
}
}
}
```
Nevertheless, I will upgrade to the new version and test it. I'll report back on the results.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org