<@U078Y59KC3B> What is the relevance of `MaxPendin...
# ask-ai
s
@RunLLM What is the relevance of
MaxPendingChunkedMessage
in the context of pulsar Go client library?
r
The
MaxPendingChunkedMessage
parameter in the Pulsar Go client library is used to manage memory pressure when handling chunked messages. It sets a limit on the number of incomplete chunked messages that can be buffered in memory at any given time. When this threshold is reached, the consumer can either silently acknowledge the oldest chunked messages or mark them for redelivery, depending on the configuration of
autoAckOldestChunkedMessageOnQueueFull
. This helps optimize memory utilization and ensures that the consumer does not get overwhelmed by too many pending chunked messages. Would you like more detail on how this parameter is configured or its impact on message processing? Sources: - https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ConsumerBuilder.java - https://nightlies.apache.org/flink/flink-docs-release-1.19/docs/connectors/datastream/pulsar/#pulsar-consumer-options 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.