How to validate chunking in consumer side #22491
Unanswered
ragaur-tibco
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How can we validate or any use-case to check chunking is working in consumer side
As mentioned in pulsar documentation
maxPendingChunkedMessage = We can limit the maximum number of chunked messages a consumer maintains concurrently by configuring the maxPendingChunkedMessage parameter.
autoAckOldestChunkedMessageOnQueueFull = When @maxPendingChunkedMessage threshold provided and the consumer reaches this threshold, it drops the outstanding unchunked-messages by silently acknowledging if autoAckOldestChunkedMessageOnQueueFull is true
expireTimeOfIncompleteChunkedMessage = If the producer fails to publish all the chunks of a message, then the consumer can expire incomplete chunks if the consumer doesn't receive all chunks during the expiration period
But want to know if there is any use-case or any debug logs from pulsar side to check and validate chunking parameters maxPendingChunkedMessage, autoAckOldestChunkedMessageOnQueueFull and expireTimeOfIncompleteChunkedMessage
if I set the maxPendingChunkedMessage=2 and enable autoAckOldestChunkedMessageOnQueueFull in consumer side, and send message from producer of size 1000bytes and configure the max chunk size to 10 bytes now how to check and validate or any debug logs for the maxPendingChunkedMessage, autoAckOldestChunkedMessageOnQueueFull and maxPendingChunkedMessage
CC: @lhotari
Beta Was this translation helpful? Give feedback.
All reactions