Open wolfstudy opened 4 years ago
The problem is that at low level we have a protocol error and the bookie is treated as broken. We should report an error earlier before trying to reach the bookie. But we cannot know the current configuration of the bookie. We could just add some max entry size on the client, probably left not configured by default.
You should see other errors before the ine you pasted
@eolivelli What about adding an endpoint that would allow configurations like that to be retrieved?
BUG REPORT
Link the issue to: https://github.com/apache/pulsar/issues/4525
Describe the bug
All configurations are the default configuration.
After starting, send a message that exceeds defaultMaxMessageSize, pulsar's broker is unavailable.
To Reproduce
test code of go:
broker error as follows:
Expected behavior
When I send a message that exceeds the maximum message allowed by pulsar, I expect pulsar's broker to fail the message instead of causing the entire broker to be unavailable.
Screenshots
If applicable, add screenshots to help explain your problem
Additional context
Add any other context about the problem here.