Lari Hotari
Lari Hotari
> > @liangyepianzhou Did we make a decision to cherry-pick this to branch-3.0 ? PIPs don't get cherry-picked by default to maintenance branches. > > @lhotari This has been discussed...
> * entry'md5 is correct in broker. But between "broker encoder -> netty channel -> bookie", the entry's md5 become error. This is most likely fixed by #22892 in Pulsar...
There are also some pending Bookkeeper issues and PRs that might be related such as apache/bookkeeper#4171 and apache/bookkeeper#4194. /cc @shoothzj
@TakaHiR07 Do you happen to use TLS between brokers and bookies? One possible workaround until Pulsar 3.0.6/3.2.4/3.3.1 is released with Bookkeeper 4.16.6 is to set `bookkeeperUseV2WireProtocol=false` in brokers. That would...
> @lhotari The issue is preserve after restart, actually data gets corrupted before storing. And we do not use TLS, but we use bookkeeperUseV2WireProtocol=true. Maybe I will try to test...
> Do not block netty threads if cursor has a lot of individuallyDeletedMessages or needs to compress the PositionInfo (separate change) @dlg99 @eolivelli Do you have any performance results to...
> @lhotari @eolivelli any objections to merging this? (PR needs an approval) I do have concerns. With asynchronous methods, there's usually a problem with back pressure. (another example: https://github.com/apache/pulsar/pull/22541#issuecomment-2071568113) Perhaps...
@visortelle do you have a chance to check this one? thanks!
A quick hack could be to add some reasonable page as the redirect target. Redirects could be made with Apache httpd syntax in https://github.com/apache/pulsar-site/blob/main/static/.htaccess @illegalnumbers any suggestions for the redirect...
Reopening since the "not found" page isn't nice. We can keep this open for contributions.