[improve][ws] Add memory limit configuration for Pulsar client used in Websocket proxy #22666
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
There's no explicit flow control in the Websocket proxy for producers. If too many messages are pushed, the proxy (or broker, if ws proxy runs with the broker) will run out of memory.
Modifications
add
webSocketPulsarClientMemoryLimitInMB
configuration option to limit the memory.by default, it is unlimited. Can be set to a value such as
64
to keep the direct memory used by the Pulsar client under 64 MB.Documentation
doc
doc-required
doc-not-needed
doc-complete