This message was deleted.
# general
s
This message was deleted.
d
Were these messages batched on the producer side, which is the default behavior? If so, then prefetching “just one” really means you prefetched one batch of messages.
u
No, we are not using batching.
d
What is the ack timeout setting for the consumers?
u
More than 2 days
d
As long as the consumer that originally received the message is still active an connected, it has up to the ack timeout to process the message before the message is considered “unprocessed” and eligible for re-delivery to a different consumer.
So in your case, the first consumer has 2 full days to process the message, as long as it is active and connected to the broker. You might want to adjust that setting downward
u
Is it assigning more than one msg due to higher ack timeout? I will reduce it and check if it’s working as expected.
👍 1
d
Message distribution still appears to be an issue, and the received queue size should be honored. I think you should file a bug report as well.
👍 2
u
@David K: I think its not related to higher ack timeout since even after reducing the timeout i am facing the same issue. I have created a Bug for the same.
👍 1