-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
splitting bundle error #5510
Comments
I seem to have reproduced this problem today. reproduce:
test-topic-n lookup broker-3
It can be seen that public/default/0xf63fffff_0xf67fffff made a split and failed the second time, throwing an exception of 500. And I found that the topic was balanced on another broker broker-2.
|
I'm running into the same issue with a custom build of Pulsar built from v2.6.2-candidate-2 tag (same as v2.6.2). The workaround is to disable bundle auto splitting and use a reasonable default number of namespace bundles..
With this workaround, Pulsar is able to handle the simple load test in a 3 node cluster (3 zk, 3 bookie, 3 broker). |
In chatting with @merlimat in the latest Office hours he felt this was fixed in 2.7 |
There's a report on Slack from a 2.7.3 user experiencing this issue. |
we experience this also in version 2.8.1 - on high load (publish rate at 220k msg/s) setup:
proxy
broker
with the workaround to disable bundle splitting |
@bpereto Thanks for reporting and sharing the relevant logs. |
There's a bundle splitting related fix in #14680 . |
Thanks @lhotari I don't think that was the issue in our case but it's certainly good to see. |
Thanks for the updates @lhotari |
Closed as stale and it seems to be fixed. Please open a new issue if it's still relevant to the maintained versions. |
Met the split bundle error when supply huge data into pulsar,block the data transfer
The text was updated successfully, but these errors were encountered: